UBO verification (6AMLD)
Find the real owners behind every business.
Regulators want to know who ultimately owns your business customers - and shell structures are designed to hide exactly that. Amani unwinds ownership chains automatically, surfaces every ultimate beneficial owner, and screens each one.
The challenge
Manual UBO research means reading registry filings across jurisdictions and mapping layered structures by hand - slow, expensive and impossible to keep current.
With Amani
- Ownership structures unwound automatically
- Every UBO above your threshold identified
- Directors and owners screened for sanctions and PEP status
- Opaque or circular structures flagged for review
- Evidence pack aligned to 6AMLD expectations
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
KYB - Business Verification
On requestVerify businesses, owners and directors in one flow.
ExploreAML / Sanctions Screening
$0.20Screen every user. Stay screened forever.
ExploreKYC
$0.35Onboard real customers. Block fraud in seconds.
ExploreDatabase Validation
On requestCheck identities against authoritative sources.
ExploreFor developers
Build this flow.
Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.
- JWT auth with refresh tokens
- Regional base URLs (EU · TR · UAE)
- HMAC-signed webhooks with retries
- 27 languages in the SDKs
verify.sh
# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
--form 'username="you@company.com"' \
--form 'password="••••••••"'
# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--form 'id_card_number="784199012345678"' \
--form 'name="Layla Haddad"'
# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"profile": PROFILE_ID,
"web_sdk_url": "https://verify.amani.ai",
"language": "en",
"return_url": "https://yourapp.com/verified"
}'
# This session runs: KYB - Business Verification, AML / Sanctions Screening, KYC, Database Validation.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › In our Node backend, create an Amani verification profile for a business customer on signup with the REST API and handle the approved/rejected webhook.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});UBO verification (6AMLD) - common questions
What ownership threshold is used?
Configurable - typically 25% for 6AMLD, but you can set a lower threshold for higher-risk segments.
How are multi-layer structures handled?
Amani traverses each layer automatically and returns the full ownership graph, flagging chains it cannot resolve.
Is ongoing monitoring available?
Yes - businesses and their officers can be re-screened on a schedule with alerts on material change.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.