Crypto Travel Rule
Send verified originator data with every transfer.
The Travel Rule requires verified identity data to travel with the value. Amani supplies the verified originator and beneficiary details, screens the counterparty VASP and the destination wallet, and records every transfer for supervision.
The challenge
VASPs must exchange accurate customer data with counterparties they may not trust, across jurisdictions with differing thresholds - while keeping transfers fast.
With Amani
- Verified originator and beneficiary identity data
- Counterparty VASP identification for transfers
- Destination wallet screened before funds move
- Threshold logic configurable per jurisdiction
- Complete, exportable transfer records
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, Amani Studio, Database Validation.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 Travel Rule - common questions
Does Amani transmit the data to counterparties?
Amani verifies and structures the required identity data; transmission runs through your Travel Rule messaging provider.
How are unhosted wallets handled?
Wallet screening plus ownership attestation flows let you apply enhanced checks to self-hosted destinations.
Are thresholds configurable?
Yes - jurisdictional thresholds are set per journey in Studio.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.