Crypto on-ramp KYC
Verify the customer. Screen the wallet.
In crypto you have two counterparties: a person and an address. Amani verifies the customer with full KYC and screens their wallets for sanctions exposure, mixer proximity and illicit-source taint - one risk profile covering both.
The challenge
Running identity providers and blockchain analytics as separate systems leaves compliance teams reconciling two views of the same customer, with no single decision point.
With Amani
- KYC, AML screening and biometrics in one flow
- Sanctions exposure traced across multiple hops
- Mixer, darknet and exploit proceeds identified
- Deposits and withdrawals cleared before settlement
- Continuous re-screening as chain activity evolves
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
For 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: KYC, AML / Sanctions Screening, Liveness, Face Match 1:N.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add Amani KYC to our React signup page using the Web SDK - ID capture plus selfie liveness, then handle the approved webhook in our Node backend.
# 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();
});Crypto on-ramp KYC - common questions
Which chains are supported?
Bitcoin, Ethereum and major EVM chains, leading stablecoins and major L2s, screened through one API.
When should wallets be screened?
At address registration, before withdrawals to new addresses, and continuously for monitored counterparties.
Can we set our own risk thresholds?
Yes - wallet risk scores carry reason codes and you configure auto-clear, review and block bands.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.