Skip to main content
Every business must clear Know Your Business verification before it can transact or hold API keys. It is completed in the app, through the KYB WebSDK launch.

What verification covers

A business is approved once it, its owners, its representatives, and its parent companies have all been reviewed and approved.
Treat the list above as informational rather than as a contract. Etherfuse tunes what is required by jurisdiction and risk, and adding a requirement changes what your customer is asked for, not your integration.

Tracking verification status

The overall status

GET /ramp/organization/{id}/kyb/status returns the same shape the webhook delivers.

The status change webhook

Subscribe to the kyb_updated webhook. It fires whenever a business’s KYB status changes and carries the organizationId, the new status, and approvedAt, so you learn the moment verification is approved or needs attention without anyone watching the app. It fires on status changes only, never on individual document or answer edits.
The organizationId identifies the business. A person is identified separately by their customerId, the sub you sign into their JWT. The two are never interchangeable.
When a customer created their own business and you only hold their sub, GET /ramp/customer/{customer_id}/organization lists the businesses they belong to, so you can find its organizationId.