Onboarding your users as a platform (B2B2C)

Onboarding your users as a platform (B2B2C)

This article is for a business that serves individual consumers on Etherfuse rails — for example, offering Etherfuse on/off-ramps inside your own app.

Two parts: your KYB, your users’ KYC

First, your company completes business verification (KYB) — company documents (incorporation, ownership/shareholding, tax ID, proof of address, business activity, source of funds, and questionnaires) plus identity verification for your beneficial owners and legal representatives. Each of your end users then needs identity verification (KYC) — but you don’t have to send them through a separate Etherfuse flow if you’ve already collected it.

Passing your existing KYC

You can pass the identity data you’ve already collected to Etherfuse via API. Whether it fully transfers depends on whether it meets our requirements — there may be a delta to fill.

Per end user we look for:

• A government ID that shows an address, or an ID plus a separate proof of address.

• CURP and RFC (tax ID).

• Full name, date of birth, email, phone, and occupation.

• A liveness check — required. If your onboarding didn’t include one, that’s the most common gap to close before KYC can be passed through.

Passing bank details

You can also pass your users’ bank account details to us via API — the user doesn’t have to enter them directly with Etherfuse.

For the KYC-submission, document-upload, and bank-account endpoints and exact payloads, see docs.etherfuse.com.

Please note: the requirements above are provided as a guide and may not be complete. Exact requirements depend on your country, account type, and a risk assessment, are versioned, and can change over time. Etherfuse may request additional information or documents during review. This list is not exhaustive and does not constitute legal or compliance advice.