Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt

Use this file to discover all available pages before exploring further.

Etherfuse supports two types of customers — personal (individual people, verified via KYC) and business (legal entities, verified via KYB). The right onboarding flow depends on which type you’re onboarding. Both work the same in sandbox as in production. You declare the customer type via accountType (personal or business) when you create the child organization. See POST /ramp/organization for the field reference.

​
Personal customers (KYC)

A personal customer is an individual person. They complete Know Your Customer verification — submit identity data, upload a selfie and a government-issued ID, and sign three agreements (electronic signature, terms and conditions, customer agreement). You have two ways to collect that data:
ApproachBest ForGuide
Hosted UI (Presigned URL)Fastest integration — Etherfuse handles identity collection, document upload, and agreement signing in one hosted pageHosted UI Flow
ProgrammaticWhite-label experience — collect data in your own UI, submit via API, full control over the customer journeyProgrammatic Flow
Start with the Hosted UI if you want the fastest path to testing. You can migrate to Programmatic later without re-onboarding existing customers.Hybrid is also common — use the programmatic API for identity and documents, then redirect the user to the presigned URL for agreements and compliance verification.
KYC Requirements (Production)In production, the following must be submitted for each personal customer:
  1. Selfie — A photo of the customer’s face
  2. Government-issued identification — A valid ID document (passport, driver’s license, national ID)
  3. Proof of address — Document showing the customer’s current address (utility bill, bank statement)
If the government-issued ID includes the customer’s address (e.g., a driver’s license), it can satisfy both requirements. After all data is submitted, Etherfuse reviews the information for accuracy before approving the customer.In sandbox, you can complete KYC using fake data — no real personal information is required.

​
Try it live

The tutorial below walks through the personal-customer KYC flow against a real environment using your API key. It demonstrates the programmatic approach with a hybrid presigned-URL step for agreements; the same shape applies to the pure hosted flow except the customer completes Steps 2–4 in the Etherfuse UI instead of via API. Toggle Sandbox/Production at the top.

​
Business customers (KYB)

A business customer is a legal entity (company, LLC, etc.). There is no per-user KYC — instead, Etherfuse Know Your Business-approves the organization as a whole, and once approved every wallet under that org is fully compliant. No selfies, ID documents, agreement signing, or presigned URLs. Business customers are onboarded only via the programmatic API. Create a child organization with accountType: "business" and Etherfuse will review and KYB-approve it: 
curl -X POST https://api.etherfuse.com/ramp/organization \
  -H "Authorization: <api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "<customer_uuid>",
    "displayName": "Acme Corp",
    "accountType": "business",
    "wallets": [
      { "publicKey": "<wallet_public_key>", "blockchain": "solana" }
    ]
  }'
See POST /ramp/organization for the full schema. The hosted UI flow is not available for business customers — POST /ramp/onboarding-url always creates a personal org.
Once Etherfuse KYB-approves the organization, you can skip the KYC, document upload, agreement signing, and presigned URL steps entirely for any wallets registered under it.

​
Reference