Skip to main content
↳ 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
  1. 1You
  2. 2You
  3. 3You
  4. 4You
  5. 5Hop
  6. 6You
    Read what is outstanding; this list drives everything that followsGET/virtual-account-groups/{gid}requirements[]
  7. 7You
    Accept the agreements, naming the signer for a businessPOST/{gid}/agreements/actionssigner_id
  8. 8You
  9. 9Hop
    Submits the entity once nothing is outstanding; no call from youunder_review
  10. 10Bank
    Verifies the entity and its people, then approves or asks for moreapproved · action_needed
  11. 11Hop
    Enables the group. Virtual accounts can now be createdstatus: enabled
  12. 12You
    Create a virtual account in the currency you needPOST/{gid}/virtual-accountsva_ pending
  13. 13Bank
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.

Troubleshooting