KYC That Respects Your Users
Verify identity once, reuse everywhere. No more uploading IDs 50 times. Reduce onboarding friction while staying compliant.
The old way vs. the new way
The Old Way
With Aho
Upload ID to every service
Verify credential once
$5+ per verification
Fraction of the cost
68% abandon during onboarding
Sub-minute verification
Data stored everywhere
User controls their data
Re-verify for every platform
Portable KYC credential
Verify in minutes, not days
# Verify user's KYC status
client = AhoSdk.verifier(api_key: ENV["AHO_API_KEY"])
# Request KYC credential from user
request = client.requests.create(
body: {
name: "KYC Verification",
purpose: "Verify identity and AML clearance"
}
)
# Check KYC verification result
response = client.responses.get(
request_uuid: "req_abc123",
uuid: "resp_xyz789"
)gem install aho-sdk · pip install aho-sdk · npm install @aho-sdk/core
Use cases
Fintech Onboarding
Reduce drop-off
Crypto Platforms
MiCA compliant
Lending Apps
Faster approvals
Investment Platforms
Streamlined KYC
Frequently Asked Questions
Traditional KYC requires users to upload ID documents to every service. With Aho, users verify once and reuse that credential everywhere. You verify, not collect.
We verify any W3C Verifiable Credential containing identity claims, including credentials from government-approved issuers, regulated KYC providers, and mobile driver's licenses (mDLs).
Yes. You can require credentials that include AML checks from regulated providers. The credential proves the user passed AML — you verify the cryptographic proof without re-running the check.
Credentials can include expiration dates and are revocable. If a user's AML status changes, the issuer revokes the credential and subsequent verifications fail.
You specify which issuers and claims you trust. Accept EU-regulated KYC providers for EU users, US-regulated providers for US users. One API, flexible trust policies.
Onboard users in minutes, not days.
No credit card required. Reduce drop-off starting today.