Create accounts
The examples on this page show the flow of creating both business and individual accounts with our API, SDKs, and Moov.js, including the use of Moov’s pre-built onboarding Drop. We strongly recommend using Moov.js’s pre-built onboarding Drop.
The examples are broken out into individual steps, but a full example is provided at the end of each section. Before you create an account, familiarize yourself with capabilities and requirements.
Get access token
This initial step is only required if you’re going to use Moov’s onboarding Drop.
Create an access token, which you’ll later include as the onboarding.token
when onboarding accounts with Drops.
|
|
Business account
The examples below have been broken up into all the small tasks needed to create a business Moov account. However, when using the API, SDKs, or Moov.js, steps 2-4 can be consolidated into one step. See the full example for details.
Create business account
You can provide a variety of information when creating an account. The example below only includes the minium required fields. The response object will include the newly created accountID
which you will need to update the account.
Create account reference
|
|
Create account reference
|
|
Create account reference
|
|
Onboarding Drop reference
With the onboarding Drop, you request capabilities when creating an account. After this step, you can jump ahead to step 4.
|
|
|
|
Request capabilities for business
Request capabilities for the account you’ve created by passing the accountID
. You can find the account ID in the create account response, or you can find it by using the list accounts GET
endpoint.
Request capabilities reference
|
|
Request capabilities reference
|
|
Request capabilities reference
|
|
Send platform agreement to business
You can send the platform agreement via a token, or manually using the accountID
. To send a token, you must generate the token and then update the account with that token. To send Moov the acceptance manually, you must capture the information from the customer and send it to Moov. Moov recommends anyone using a server integration update the terms of service using the manual method.
Generate token reference and update account reference
|
|
|
|
Update account reference
|
|
Terms of Service Drop reference
|
|
|
|
Create representatives
Moov must verify business representatives before a business account send funds or collect funds from other accounts. A beneficial owner is any individual with ≥25% ownership of the business (owner), or someone with significant responsibility to control or manage the business (controller).
An account is not required to have an owner, but must have at least one controller. An account can have a maximum of 7 representatives.
Add a representative reference
|
|
Add a representative reference
|
|
Add a representative reference
|
|
Update account with beneficial owners
Update the account to alert Moov that you have finished creating representatives. At least one controller should have been created in step 4.
Update account reference
|
|
Update account reference
|
|
Update account reference
|
|
Additional underwriting and verification
Depending on the account and capabilities requested, Moov might require additional verification and underwriting. You will receive alerts for any missing data in the Dashboard.Create business account full example
You can consolidate steps 2 through 4 using the create account POST
endpoint. The below example includes all the fields you can send to Moov in one step when creating a business account. After creating an account, you would still need to add representatives and provide beneficial owner confirmation (starting at steps 5 and 6).
Any additional verification and underwriting requirements will be listed in the Dashboard.
Create account reference
|
|
Create account reference
|
|
Create account reference
|
|
Individual account
The examples below have been broken up into all the small tasks needed to create an individual Moov account. However, when using the API, SDKs, or Moov.js, steps 2-4 can be consolidated into one step. See the full example for details.
Create individual account
You can provide a variety of information when creating an account. The example below only includes the minium required fields. The response object will include the newly created accountID
which you will need to update the account.
Create account reference
|
|
Create account reference
|
|
Create account reference
|
|
Onboarding Drop reference
With the onboarding Drop, you request capabilities when creating an account. After this step, you can jump ahead to step 3.
|
|
|
|
Request capabilities for individual
Request capabilities for the account you’ve created by passing the accountID
. You can find the account ID in the create account response, or you can find it by using the list accounts GET
endpoint.
Request capabilities reference
|
|
Request capabilities reference
|
|
Request capabilities reference
|
|
Send platform agreement to individual
You can send the platform agreement via a token, or manually using the accountID
. To send a token, you must generate the token and then update the account with that token. To send Moov the acceptance manually, you must capture the information from the customer and send it to Moov. Moov recommends anyone using a server integration update the terms of service using the manual method.
Generate token reference and update account reference
|
|
|
|
Update account reference
|
|
Terms of Service Drop reference
|
|
|
|
Create individual account full example
You can consolidate steps 1 through 3 using the create account POST
endpoint. The below example includes all the fields you can send to Moov in one step when creating an individual account.
Any additional verification and underwriting requirements will be listed in the Dashboard.
Create account reference
|
|
Create account reference
|
|
Create account reference
|
|
Next steps
After you’ve successfully created accounts, the next step is to link a funding source like a card or bank account so you can start moving money.