↳ Two gates stand between a new group and a usable one: the provider approves onboarding (
onboarding_status: approved), then Hop enables the group (status: enabled). A business is signed for by an associated person marked is_signer; an individual signs as itself and skips step 3.Youthe API callerHopautomaticBankpartner bank
- 1YouPlatform customers: create the account for the end customer, with its identity and associated persons in the same callPOST/customers/{cid}/accountsacct_
- 2YouSet the account identity: legal name, registration number, incorporation date, registered addressPATCH/customers/{cid}/accounts/{aid}
- 3YouAdd the people behind the entity, at least one with is_signer (business only)POST/accounts/{aid}/associated-personsaap_
- 4YouOpen the group. Safe to call before the identity is set; it returns with a requirementPOST/accounts/{aid}/virtual-account-groupsvag_
- 5Hop
- 6YouRead what is outstanding; this list drives everything that followsGET/virtual-account-groups/{gid}requirements[]
- 7YouAccept the agreements, naming the signer for a businessPOST/{gid}/agreements/actionssigner_id
- 8YouUpload each requested document against its requirement keyPOST/{gid}/documentsdoc_
- 9HopSubmits the entity once nothing is outstanding; no call from youunder_review
- 10BankVerifies the entity and its people, then approves or asks for moreapproved · action_needed
- 11HopEnables the group. Virtual accounts can now be createdstatus: enabled
- 12YouCreate a virtual account in the currency you needPOST/{gid}/virtual-accountsva_ pending
- 13BankIssues the bank details; the virtual account becomes activeIBAN · account number
Known gaps: steps 9 to 11 and 13 have no webhook and no stated service time, so poll Get Virtual Account Group and Get Virtual Account with backoff. An approved group can return to
action_needed after go-live, so keep reading requirements for the life of the account. Some group types charge a creation fee at step 12 that is not readable before the call.