This guide will cover the basics of applying to open new bank accounts (both business and personal) as well as funding those accounts with an initial deposit.
/apply/person_application
/apply/business_application
/apply/deposit
/apply/account_application
/account
/account_product
/person
/business
POST
request to the person_application
endpoint, passing a Person Application object containing the personal information of the individual who will be tied to the account.
id
property referencing this application. Note the id
value as it will be used in subsequent steps.
POST
request to the business_application
endpoint, passing in a Person Applications object for each person who will be associated with the account as part of the person_applications
array.
Note the id
property should contain the id
of the Person Application for this person.
The format for the Person sub-object is as follows:
POST
request to the deposit
endpoint passing a Deposit object containing information about the account the funds will be drawn from.
/account_product
endpoint to choose an appropriate Account Product
id
property. Select one and note its id
value.
submitted
, then moving to status processing
. Depending on the results of the KYC (Know Your Customer) process, the Account Application will move to status approved
, rejected
, or manual_review
.
Once an Account Application passes KYC, then an account is created and the account_id
field is populated. The account is not fully setup until the status of the account is “approved”, signifying that the account setup process is complete.
POST
request to the account_application
endpoint, passing an Account Application object containing information about the associated Person Application(s), the ID of the primary Person Application, and the ID of the Account Product being applied for.
Note: See the section Account application with initial deposit for an example of including a deposit with the Account Application.
POST
request to the account_application
endpoint, passing an Account Application object containing two person application records for person_applications
assigning both with owner
and signer
roles and ID of the Account Product being applied for. Set one of the two person application IDs as the primary Person Application.
POST
request to the account_application
endpoint, passing an Account Application object containing the ID of the Business Application, the ID of the primary Person Application, and the ID of the Account Product being applied for.
Note: See the section Account application with initial deposit for an example of including a deposit with the Account Application.
deposit_id
property to the Account Application object listing the ID of the Deposit. This works the same for both personal and business account applications.
See the section Create a Deposit for information on creating a Deposit.
id
of the Account Application. To do this, make a GET
request to the account_application/:id
endpoint.
account_id
(found in the response from the account_application/:id
endpoint outlined in the previous section). To do this, make a GET
request to the account/:account_id
endpoint.
person_ids
and business_ids
properties in an Account object let you retrieve information about account owners (persons and businesses respectively).
Note that Person and Business objects are separate from the Person Application and Business Application objects. Information about persons and businesses are expected to change (such as changing a name or address) and reflect current data, while Person Application and Business Application objects are static and are a snapshot of these entities at the time that they applied for an account.
GET
request to the person/:id
endpoint passing the person_id
which is found in the Account object.
GET
request to the business/:id
endpoint passing the business_id
found in the Account object.
More information on testing can be found here.
tin
property of each Person Application object submitted with the application must be set to one of the following values before submitting the Account Application. Note that all of the tin
properties must be set to the same value. An x
indicates any digit.
Status | Test TIN |
---|---|
Approved | 1xx-xx-xxxx |
Manual Review | 2xx-xx-xxxx |
Processing | 3xx-xx-xxxx |
Rejected | 4xx-xx-xxxx |
Submitted | 5xx-xx-xxxx |
tin
property of each Person Application object and the tin
property of the Business Application object submitted with the application must be set to one of the following values before submitting the Account Application. Note that all of the tin
properties must be set to the same value. An x
indicates any digit.
Status | Test TIN |
---|---|
Approved | 1x-xxxxxxx |
Manual Review | 2x-xxxxxxx |
Processing | 3x-xxxxxxx |
Rejected | 4x-xxxxxxx |
Submitted | 5x-xxxxxxx |