Skip to main content
Onboarding an end customer is requirements-driven: required fields, document types, and — for businesses — associated-person roles come from the requirements returned by Get Account. There is no client-facing submit step — Hop submits business applications automatically once all requirements are satisfied, and individual accounts are submitted at create. Use the control below to switch between the business (KYB) and individual (KYC) flows.
End-customer type
↳ End-customer type is chosen at account creation (type: “business” | “individual”) and selects the flow: KYB for businesses, KYC for individuals. Business requirements (fields, entity documents, associated persons) come from the requirements returned by Get Account; individuals submit the full profile at create and start under_review, with identity captured in the hosted verification session — no document upload. Agreements are separate account-scoped actions that gate activation independently.
POSTwriteGETreadwebhookevent you receiveHostedHop-hosted flowacct_resource— Platform— Hop— End customer
Platformyou
1Create the account — opens a draft KYB applicationPOST/customers/{cid}/accountsaccount.createdacct_›
2Get Account — the source of truth for what is neededGET/…/accounts/{id}requirements›
3Add required UBOs, directors, and control personsPOST/…/associated-personsaap_›
4Create a hosted verification session and share its linkPOST/…/verification-sessionHosted verification›
5Upload entity documents against each requirement_keyPOST/…/accounts/{id}/documentsdoc_›
11On approval, provision virtual accounts and go livePOST/accounts/{id}/virtual-accountskyc_status: approved
HopAPI · verification
6Hop re-checks requirements after every change; submits when readyready_for_submissionkyc_status: under_review›
7Hop runs sanctions, PEP, document, and identity reviewVerification review›
8Hop emits account.updated with the KYB outcomeaccount.updated›
9Approved or rejected — rejection is terminalkyc_status: approvedrejection_reasons›
End customerbusiness & its people
10Handle assigned agreements as a separate activation gateGET/…/agreementsPOST/…/agreements/actionsaagr_›
Platformyou
1Create the account with the full profile — create is the submissionPOST/customers/{cid}/accountskyc_status: under_reviewacct_
2Get Account — the source of truth for what remainsGET/…/accounts/{id}requirements
3Create a hosted verification session for the account holder and share its linkPOST/…/verification-sessionHosted verification
9On approval, provision virtual accounts and go livePOST/accounts/{id}/virtual-accountskyc_status: approved
HopAPI · verification
5Hop runs sanctions, PEP, document, and identity reviewVerification reviewkyc_status: under_review
6Hop emits account.updated with the KYC outcomeaccount.updated
7Approved or rejected — rejection is terminalkyc_status: approvedrejection_reasons
End customerthe individual
4Account holder completes the identity document and selfie checkHosted WebSDK · ID + selfie
8Handle assigned agreements as a separate activation gateGET/…/agreementsPOST/…/agreements/actionsaagr_

Tip: select any card to open its API reference or guide. The end-customer type control switches the flow. Scroll down to follow the flow ↓

Business account creation opens a draft KYB application — Hop re-checks the requirements after every change and starts verification review automatically once all requirements are met. Individual account creation is itself the KYC submission — the account starts under review and only the account holder’s hosted verification session remains. Agreements are independent account-scoped actions accepted by an authorized signer and gate activation separately.