> ## Documentation Index > Fetch the complete documentation index at: https://apidocs.hopnow.io/llms.txt > Use this file to discover all available pages before exploring further. # Virtual Account Onboarding
Start with whose account you are onboarding, then identify whether the virtual account holder is a business or an individual. Your customer model determines which account to use; the holder's identity determines the verification requirements.
## Choose your customer model ### Direct customers Use your existing account to open virtual accounts in your own name. Retrieve its `id` with [List Accounts](/fx/api-reference/accounts/list-accounts), then set or complete your identity profile with [Update Account](/fx/api-reference/accounts/update-account-identity). ### Platform customers Use [Create Account](/fx/api-reference/accounts/create-account) to create one account per end customer, supplying that customer's identity profile. For a business, you can include associated persons in the same request. If the end customer already has an account, reuse it. Their virtual accounts are opened in their name. To open virtual accounts for your platform itself, use your existing fee-collection account and your platform's own identity profile. ## Identify the virtual account holder Both customer models use the same identity types. Set `type` to `business` or `individual` when creating or updating the account's identity profile. Once set, this identity type cannot be changed. | Holder | Identity `type` | Verification and signing | | - | - | - | | [Business](#business-account) | `business` | Verify the business and its associated persons. An associated person with `is_signer: true` signs agreements; pass their ID as `signer_id`. | | [Individual](#individual-account) | `individual` | Verify the individual. There are no associated persons. The individual signs for themselves; omit `signer_id`. | Business and individual describe the account holder's identity. The virtual account group's `type` selects a service from [List Group Types](/fx/api-reference/virtual-account-groups/list-group-types). ## Accounts, groups and virtual accounts An **account** stores the identity of the business or individual selected above. A **virtual account group** tracks that account's onboarding requirements, approval, and activation for a group type. You can onboard the same account for multiple group types, with one group per type. Each group is onboarded and enabled separately. Repeating [Create Virtual Account Group](/fx/api-reference/virtual-account-groups/create-group) for the same account and type returns the existing group. A **virtual account** belongs to one group and provides bank details in the account holder's name, with its own balance in one currency. Once the group has `onboarding_status: approved` and `status: enabled`, you can [create virtual accounts](/fx/api-reference/virtual-accounts/create-virtual-account) in its supported currencies, including multiple virtual accounts in the same currency. ## Complete onboarding Follow the business or individual flow below for the account you selected. If its identity profile and any associated persons are already complete, continue to **Open the group**. After you open the group, [Get Virtual Account Group](/fx/api-reference/virtual-account-groups/get-group) returns the outstanding `requirements`. Clear them item by item. Hop submits the account for review automatically; there is no submit call.
Youthe API caller Hopautomatic Bankpartner bank
### Business account
  1. Identity
  2. 1 You
    Set the account identity: legal name, registration number, incorporation date, registered address PATCH/customers/\{cid}/accounts/\{aid}
  3. 2 You
    Add the people behind the entity: at least one with is\_signer POST/accounts/\{aid}/associated-persons aap\_
  4. Open the group
  5. 3 You
    Open the group: safe to call before the identity is set, it just comes back with a requirement POST/accounts/\{aid}/virtual-account-groups vag\_
  6. 4 Hop
    Raises the agreements the entity must sign agr\_
  7. Clear requirements
  8. 5 You
    Read what is outstanding. This list drives everything that follows GET/virtual-account-groups/\{gid} requirements\[]
  9. 6 You
    Accept the agreements, naming the signer POST/\{gid}/agreements/actions signer\_id required
  10. 7 You
    Upload each requested document against its requirement key POST/\{gid}/documents doc\_
  11. Review
  12. 8 Hop
    Submits the entity once nothing is outstanding. No call from you under\_review
  13. 9 Bank
    Verifies the entity and its people, then approves or asks for more approved · action\_needed
  14. Go live
  15. 10 Hop
    Enables the group. Virtual accounts can now be created status: enabled
  16. 11 You
    Create a virtual account in the currency you need POST/\{gid}/virtual-accounts va\_
  17. 12 Bank
    Issues the bank details; the virtual account leaves pending IBAN · account number
### Individual account
  1. Identity
  2. 1 You
    Set the account identity: name, date of birth, nationality, address, tax residence and due-diligence answers PATCH/customers/\{cid}/accounts/\{aid}
  3. Open the group
  4. 2 You
    Open the group. No associated persons are needed for an individual POST/accounts/\{aid}/virtual-account-groups vag\_
  5. 3 Hop
    Raises the agreements the person must sign agr\_
  6. Clear requirements
  7. 4 You
    Read what is outstanding. For an individual this is profile fields and identity documents GET/virtual-account-groups/\{gid} requirements\[]
  8. 5 You
    Accept the agreements: omit signer\_id, the person signs as themselves POST/\{gid}/agreements/actions no signer\_id
  9. 6 You
    Upload each requested document against its requirement key POST/\{gid}/documents doc\_
  10. Review
  11. 7 Hop
    Submits the person once nothing is outstanding. No call from you under\_review
  12. 8 Bank
    Verifies the person, then approves or asks for more approved · action\_needed
  13. Go live
  14. 9 Hop
    Enables the group. Virtual accounts can now be created status: enabled
  15. 10 You
    Create a virtual account in the currency you need POST/\{gid}/virtual-accounts va\_
  16. 11 Bank
    Issues the bank details; the virtual account leaves pending IBAN · account number
## What each requirement means Everything after the group is opened is driven by the `requirements` list on [Get Virtual Account Group](/fx/api-reference/virtual-account-groups/get-group). Four kinds appear: | `type` | What to do | | - | - | | `account_profile` | Fields are missing from the identity profile. `account_profile.required` means the account has no complete profile yet; other keys name the fields still needed. Clear both with [Update Account](/fx/api-reference/accounts/update-account-identity). | | `associated_person` | Either the account has no associated persons yet, or a named person is missing details. Business accounts only. | | `document` | A file is needed. `accepted_document_types` says which, and `associated_person_id` says whose when it targets a person. | Saving an identity profile or an associated person resumes onboarding on its own, so poll the group rather than re-creating anything. ## Troubleshooting | Signal | Meaning | Do this | | | - | - | - | - | | `onboarding_status` is `rejected` or `closed` | Terminal: the group never leaves it, and a new one cannot be opened for the same provider on that account. | N/A | | | `action_needed` with an empty `requirements` list | The provider has not yet told Hop what it wants. | Poll; the list fills in. | | | An `associated_person` requirement on an account with no people | No individual associated with the account. | Add a person with [Create Associated Person](/fx/api-reference/associated-persons/create-associated-person). | |