無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
リセラーが負うもの
KYCを自社ブランドで提供。基盤となる複雑なシステムは不要です。
スタイルエディターで、色、タイポグラフィ、正方形・長方形のロゴ、カスタムドメインを設定できます。各ワークフローで「カスタムスタイルを含める」を切り替えるだけです。エンドユーザーには貴社のブランド、ドメイン、フローが表示され、貴社はDiditからiBeta Level 1 PAD（Presentation Attack Detection）、スペインのTesoro / SEPBLAC認証、SOC 2 Type 1、ISO/IEC 27001を継承できます。毎月500件まで無料で検証できます。
仕組み
サインアップから認証済みユーザーまで、4つのステップで完了します。
- ステップ 01
ワークフローを作成する
ID、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェックを選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIに投稿します。条件分岐やA/Bテストもコード不要で実行できます。
- ステップ 02
統合する
当社のWeb、iOS、Android、React Native、またはFlutter SDKを使用してネイティブに組み込むか、ホストされたページにリダイレクトするか、またはメール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送信するだけです。あなたのスタックに合った方法を選択してください。
- ステップ 03
ユーザーがフローを完了する
Diditは、カメラ、照明キュー、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。結果は2秒以内に得られます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることもできます。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを独自の方法で管理することも可能です。
01 · スタイルエディター
ノーコードでブランドを切り替え。
色、タイポグラフィ、正方形・長方形ロゴ、ボーダー半径、Diditログイン画面の表示/非表示を設定できます。プレビューは、Diditではなく、お客様のブランドに合わせたホスト型UIで表示されます。アカウントごとに一度設定すれば、各ワークフローに適用されます。
ホワイトラベルモジュールDidit · Style Editor
Swap colours, type, logo.
Your brand
Verify your identity
- Brand colours
- Typography
- Square + rect logos
- Border radius
- Login screen on / off
02 · カスタムドメイン
verify.yourbrand.comでホスト。
CNAMEターゲットはverify.didit.me、TLS証明書はLet's Encrypt経由で自動プロビジョニングされ、HSTSはデフォルトで有効です。ビジネスコンソール内で検証が完結するため、お客様側での運用は不要です。
ホワイトラベル ドキュメントDidit · Custom domain
Host on your domain.
DNS record
typeCNAME
hostverify.yourbrand.com
targetverify.didit.me
ttl300 s
TLS · auto
issuerLet's Encrypt
statusActive
auto_renew30 days
hstsEnabled
Verified inside the Business Console · zero ops.
03 · SDK · 5つのプラットフォーム
1つのブランド。あらゆるランタイムで。
Web、iOS (Swift)、Android (Kotlin)、React Native (TurboModules)、Flutterの全プラットフォームで同じスタイルエディター設定が適用されます。SDKは無料で、ホワイトラベル料金にはこれらすべてのブランド設定が含まれます。
ワークフローオーケストレーターDidit · SDKs
One brand. Five surfaces.
- Web SDKReact, Vue, vanilla
- iOS · AndroidNative Swift + Kotlin
- React NativeTurboModules
- FlutterDart package
Same Style Editor config applies across all five.
04 · ワークフローごとのブランド設定
1つのアカウントでブランドと非ブランドを混在。
顧客向けワークフローではカスタムスタイルをONに、社内管理フローではOFFに切り替えます。複数のブランドを扱うリセラーに最適です。1つのDiditアカウントで、複数のエンド顧客ブランドをワークフローごとにスタイル設定できます。
ワークフロー ドキュメントDidit · Workflow Builder
Per-workflow brand on / off.
WorkflowCustom styleOutcome
- wf_signup · consumerONPass
- wf_kyc_step_upONPass
- wf_internal_adminOFFPass
- wf_partner_b · resellerON · brand BPass
- wf_sandbox · debugOFFPass
Multi-brand on one account · ideal for resellers.
05 · リセラー向け料金
$0.53 cost in. You pick the sticker.
Didit KYCバンドル $0.33 + ホワイトラベル料金 $0.20 = 1チェックあたり$0.53。お客様の顧客には$0.99〜$1.49で提供し、差益を確保できます。大量利用の場合はボリュームディスカウントが適用されますので、営業担当にご相談ください。
ユーザー認証モジュールDidit · Reseller margin
Cost in. Price out.
LineAmountNote
- Didit KYC bundle$0.33Floor
- White-label fee+ $0.20Per check
- Your cost$0.53Total in
- Your sticker price$0.99 - $1.49Out
- Your margin · per check$0.46 - $0.96Net
Volume discount kicks in at scale. Talk to sales.
06 · 監査証跡の保持
あなたのブランド。同じコンプライアンス。
iBeta Level 1 PAD、スペインのTesoro / SEPBLAC認証、SOC 2 Type 1、ISO/IEC 27001、GDPR準拠、デフォルトで5年間保持。ブランドを変更しても、基盤となるコンプライアンス基準は変わりません。
AMLスクリーニングモジュールDidit · Audit retained
Your brand. Same compliance.
- iBeta Level 1 PADSame liveness ceiling
- Tesoro · SEPBLACEU-government attested
- SOC 2 · ISO 27001Inherited by your stack
- 5-year retentionConfigurable upward
Sub-process disclosure available on request.
連携
1つのセッション。あなたのブランド。あなたのドメイン。
ブランド化されたセッションを開始し、署名済みの検証結果を受け取ります。エンドユーザーがDiditを目にすることはありません。
POST /v3/session/ブランド化
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_signup_branded",
"vendor_data": "end-user-42",
"metadata": { "tenant_id": "ブランドB" }
}'201作成済みお客様のカスタムドメインでホストされたURLを返します。
スタイルエディターとワークフローごとのトグルでブランディング。API変更は不要です。ドキュメント →
GET /v3/session/{sessionId}/decision/判定
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns:
{
"ステータス": "承認済み",
"AML": { "ステータス": "承認済み" }
}200OKステータス：承認済み・却下・審査中・再提出・期限切れ
UIのブランディング方法に関わらず、同じ/v3/コントラクトを使用します。ドキュメント →
エージェント対応統合
ホワイトラベルKYC製品をプロンプト一つでリリース。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。ブランド、ドメイン、ワークフローモジュールを入力すると、エージェントがスタイルエディターを設定し、署名済みウェブフックを接続し、ブランド化されたフローをデプロイします。
didit-integration-prompt.md
You are integrating Didit white-label KYC. You're either reselling identity verification to your own customers under your brand, or embedding KYC inside your SaaS product so the end-user never sees Didit. Either way, the verification stack is Didit's; the visible brand is yours.
Three pillars:
1. Configure your brand once in the Style Editor — colours, typography, square + rectangular logos, optional custom domain.
2. Toggle Include custom style ON for every workflow that should ship under your brand. Leave it OFF for internal admin flows.
3. Open POST /v3/session/ as usual. The hosted UI returns under your brand on your domain.
Cost:
- Didit KYC bundle: $0.33 per check (Sessions API floor)
- White-label fee: $0.20 per check (adds branding + custom domain + per-workflow style toggle)
- Reseller cost in: $0.53 per check
- Mark up to your buyer as you choose — published rate at scale, custom contracts above 100k/month
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- White-label add-on enabled on your account (talk to sales to switch it on).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder that bundles the modules you ship (typically ID Verification + Passive Liveness + Face Match 1:1 + AML Screening) with Include custom style ENABLED.
- Optional: custom domain (e.g. verify.yourbrand.com) configured in the Business Console — Didit handles the CNAME target + TLS cert via Let's Encrypt.
STEP 1 — Configure brand in the Style Editor (no code)
Console → White Label → Style Editor:
Colors: buttons, text, panels, backgrounds
Typography: fonts that match your brand
Logos: square + rectangular uploads
Layout: border radius for panels and buttons
Login: show or skip the Didit login screen
Domain: add verify.yourbrand.com (CNAME target = verify.didit.me; TLS auto-provisioned)
STEP 2 — Enable custom style on the workflow
Console → Workflows → <your workflow> → Settings → Options:
Toggle Include custom style ON. Without this, the workflow ships with default Didit branding.
Repeat per workflow. You can mix branded + unbranded workflows on the same account — useful for an internal admin flow that doesn't need the customer brand.
STEP 3 — Open a session as usual
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id with Include custom style ON>",
"vendor_data": "<your end-user id, max 256 chars>",
"callback": "https://<your-app>/kyc/callback",
"metadata": {
"purpose": "white_label_onboarding",
"tenant_id": "<your reseller tenant id if multi-brand>"
}
}
Response: 201 Created with the hosted session URL — under YOUR domain if you set one. Sub-2-second median verdict on completion.
STEP 4 — Read the signed webhook on completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your end-user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"aml": { "status": "Approved", "hits": [] }
}
Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.
On Approved → onboard the end-user. On Declined → reject. On In Review or Resubmitted → hold + route to your compliance team.
STEP 5 — Multi-brand on one account (reseller pattern)
When you serve multiple end-customer brands from a single Didit account:
- Create one workflow per end-customer brand
- Configure each workflow with the customer's brand style (or use the Style Editor presets per workflow if your account supports it)
- On POST /v3/session/, pick the workflow_id that matches the end-customer's brand
The end-customer sees their own brand; you see one consolidated invoice per month. Didit's MCP (Model Context Protocol) server is included free for programmatic per-tenant workflow management.
STEP 6 — Audit + compliance retained
Swapping the brand does not change the underlying compliance bar. Every session is still:
- iBeta Level 1 PAD (Presentation Attack Detection) certified on liveness
- Backed by Spain's Tesoro / SEPBLAC attestation (only EU member-state government attestation of safer-than-in-person verification)
- Aligned with SOC 2 Type 1 + ISO/IEC 27001 + GDPR (General Data Protection Regulation)
- Logged with X-Signature-V2 webhook signing on every event
- Retained 5 years post-relationship by default per the EU Anti-Money-Laundering package; configurable upward per your supervisor's guidance
Sub-processor disclosure available on request for your DPA (Data Processing Agreement).
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Verify X-Signature-V2 on every payload.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Don't transform them.
- The white-label add-on is a per-account feature — talk to sales to enable it. Once enabled, the Style Editor + custom-domain pipeline is no-code.
- Custom domain TLS auto-renews 30 days before expiry. Monitor the cert status in the Console.
- Some end-user browsers (mobile in-app webviews) constrain custom domains — keep verify.didit.me as a fallback for these edge cases.
Read the docs:
- https://docs.didit.me/console/white-label
- https://docs.didit.me/console/workflows
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.さらに詳しい情報が必要ですか？モジュールの全ドキュメントをご覧ください。docs.didit.me →
設計段階からのコンプライアンス
ワンクリックで新しい国に進出。 面倒な作業は私たちにお任せください。
私たちは現地法人を設立し、ライセンスを取得し、ペネトレーションテストを実施し、認証を取得し、新しい規制すべてに準拠します。新しい国で認証を提供するには、トグルを切り替えるだけです。220以上の国で稼働しており、四半期ごとに監査とペネトレーションテストを実施しています。EU加盟国の政府が対面認証よりも安全だと正式に認めた唯一のIDプロバイダーです。
セキュリティ＆コンプライアンス資料を読むEU金融サンドボックス
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
情報セキュリティ · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
設計段階からのEU準拠
実績データ
実績データ
- $0.00チェックあたりのコスト, KYCバンドル$0.33 + ホワイトラベル手数料$0.20。お客様の顧客に上乗せできます。
- 0 SDKsWeb、iOS、Android、React Native、Flutter, すべて同じブランドで提供されます。
- Per WFカスタムスタイル切り替え機能を含む, 1つのアカウントでブランド付きとブランドなしのワークフローを利用できます。
- 0すべてのアカウントで毎月無料の認証を提供します。
3つのティア、1つの料金表
無料で開始。従量課金。エンタープライズまで対応。
毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
最も人気
従量課金
従量課金
使った分だけお支払い。25以上のモジュール。モジュールごとの公開価格、月額最低料金なし。
- フルKYC（本人確認 + 生体認証 + IP / デバイス）が$0.33
- 10,000以上のAMLデータセット, 制裁、PEP、ネガティブ情報
- データベース検証のための1,000以上の政府データソース
- トランザクションモニタリングが1トランザクションあたり$0.02
- ライブKYBが1企業あたり$2.00
- ウォレットスクリーニングが1チェックあたり$0.15
- ホワイトラベル検証フロー, あなたのブランド、私たちのインフラ
エンタープライズ
エンタープライズ
カスタムMSA & SLA。大量利用や規制対象プログラム向け。
- 年間契約
- カスタムMSA、DPA、SLA
- 専用SlackおよびWhatsAppチャンネル
- オンデマンドの手動レビュー担当者
- リセラーおよびホワイトラベル条件
- 限定機能とパートナー連携
- 専任CSM、セキュリティレビュー、コンプライアンスサポート
無料で開始 → チェック実行時のみ支払い → カスタム契約、SLA、データレジデンシーが必要な場合はエンタープライズプランへ。
FAQ
よくある質問
What is Didit?
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
- Fast, sub-2-second p99 on every session
- Reliable, in production with 1,500+ companies across 220+ countries
- Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
What's a white-label KYC, in plain English?
It's an identity-verification product that runs under your brand, your colours, your logo, your domain, but uses someone else's verification stack under the hood. The end-user never sees the underlying vendor.
Two flavours you can ship:
- Reseller, your business is identity verification (or a vertical wrapper of it). You charge customers a per-check rate that's higher than your cost, and the margin is the business model. Common for SaaS aggregators, niche compliance plays, regional resellers in markets the big vendors don't serve well.
- Embedded, you're a SaaS / fintech / platform whose product includes KYC as one feature among many. You don't want your end-users to bounce into a Didit-branded flow mid-onboarding; you want the verification to feel like part of your product.
The Didit recipe handles both with the same Style Editor + per-workflow toggle.
What can I actually customise?
Six categories, all no-code via the Business Console Style Editor:
- Colours, buttons, text, panels, backgrounds. Every colour element is a token.
- Typography, fonts that match your brand. Upload custom font files or pick from a curated list.
- Logos, square and rectangular logo uploads. Used on hosted screens, in-app SDK headers, and email confirmations.
- Layout, border radius for panels and buttons. Match your design language (sharp corners or rounded).
- Login screen, show or skip the Didit login screen at session start.
- Custom domain, host on
verify.yourbrand.cominstead ofverify.didit.me. CNAME + TLS handled inside the Console.
The Style Editor previews live as you change tokens. Once you save, toggle Include custom style on the workflow you want branded, that's the activation gate.
How fast is the verification for my end user?
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
Does the white-label cover the SDKs too?
Yes. The same Style Editor configuration applies across all five Didit SDKs, Web (React, Vue, vanilla JS), iOS (Swift), Android (Kotlin), React Native (TurboModules), and Flutter (Dart). The SDKs are free; the white-label fee covers branding across every surface.
In practice: you set colours, type, logos, and radius once. The SDK reads the same brand config from your account, the hosted flow reads the same config, and your end-user gets a consistent branded experience whether they're in a mobile app, a webview, or a desktop browser.
What happens if a user fails, abandons, or expires?
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.In Progress, user is mid-flow.Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.Abandoned, user opened the link but did not finish in time. Re-engage or expire.Expired, the session link aged out. Create a new session.
A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Where does my customer data live and how is it protected?
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Is Didit compliant for my industry?
Didit ships compliant by default for the regulators that matter to identity infrastructure:
- GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
- AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
- eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
- MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
- DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
- BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
- UK Online Safety Act, age-gating and child-safety obligations.
- FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.
Detailed memo, every certificate, every regulator letter: /security-compliance.
How fast can I integrate and start verifying users?
- 60 seconds to a sandbox account at business.didit.me, no credit card.
- 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
- A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.
Three integration paths, pick whichever fits your stack:
- Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
- Redirect the user to the hosted verification page, zero SDK.
- Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
Do I keep the underlying compliance attestations?
Yes. Swapping the brand does not change the underlying compliance posture:
- iBeta Level 1 PAD, Didit's Passive Liveness is iBeta Level 1 certified, meaning it has been independently tested against printed photos, screen replays, masks, and deepfakes
- Tesoro / SEPBLAC, Didit is the only identity provider formally attested by Spain's Tesoro (under SEPBLAC, Spain's financial-intelligence unit) as a safer-than-in-person verification mechanism, for purposes of the EU Anti-Money-Laundering package
- SOC 2 Type 1, independent audit of Didit's security controls
- ISO/IEC 27001, international security-management standard
- GDPR alignment, General Data Protection Regulation by design (data minimisation, lawful basis, DSAR support)
Under your white-label, all of these flow through to your customer. Didit provides sub-processor disclosure on request for your DPA (Data Processing Agreement).
How does this fit with Didit's MCP server and the Workflow Builder?
Both are free, both work with the white-label add-on.
- Workflow Builder, drag-and-drop composer for KYC + AML + KYB + Wallet Screening modules. Per-workflow Include custom style toggle lives here. Edit rules and module selection without redeploying your app.
- Didit MCP (Model Context Protocol) server, exposes the same Didit primitives to AI coding agents (Claude Code, Cursor, Codex, Replit Agent, Devin, Aider). Useful for a small reseller team that wants to automate per-tenant workflow provisioning, branded-flow templating, or scripted onboarding tests.
The net: you don't need a large engineering team to ship a white-label KYC product. The Style Editor handles brand, the Workflow Builder handles modules, the MCP server handles automation, and the /v3/ API handles the verification itself.
How fast can a small team launch?
Four wires, one afternoon for a vertical-slice; a week for production:
- Open
business.didit.me, sandbox key in 60 seconds, no credit card - Enable the white-label add-on (talk to sales) and open the Style Editor, configure brand, upload logos, add custom domain (CNAME at your DNS provider)
- Build the workflow in the Workflow Builder with the modules you ship (typically ID + Liveness + Face Match + AML), toggle Include custom style ON
- Wire
POST /v3/session/+ the signed webhook (X-Signature-V2HMAC SHA-256) into your onboarding flow
For a multi-tenant reseller, add: one workflow per end-customer brand, per-tenant Style Editor configuration, a routing layer that picks the right workflow_id per inbound request. The MCP server scripts these end-to-end.