Skip to main content
Onboarding a business end customer is requirements-driven: required fields, entity-document types, and associated-person roles come from the requirements returned by Get Account. There is no client-facing submit step — Hop submits automatically once all requirements are satisfied. Use the control below to walk the three review outcomes.
Review outcome
↳ Business account (type: “business”). Required fields, entity-document types, and associated-person roles come from the requirements returned by Get Account. Agreements are separate account-scoped actions that gate activation independently of automatic KYB submission readiness.
POSTwriteGETreadPATCHupdatewebhookevent 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_›
11Account activated — ready to provision a virtual accountCorrect the requested items; automatic review resumesOnboarding stops — rejected is terminalkyc_status: approvedPOST/accounts/{id}/virtual-accountsPATCH/…/accounts/{id}POST/…/documentsrejection_reasons
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 — KYB verification passedAction needed — correct items, review resumes automaticallyRejected — terminalaccount.updatedkyc_status: approvedaccount.updatedPATCH/…/accounts/{id}account.updatedrejection_reasons›
End customerbusiness & its people
10Handle assigned agreements as a separate activation gateGET/…/agreementsPOST/…/agreements/actionsaagr_›

Tip: select any card to open its API reference or guide. The review-outcome control changes steps 9 and 11. Scroll down to follow the flow ↓

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. Agreements are independent account-scoped actions accepted by an authorized associated person and gate activation separately.