Onboard a Business
What is a Business?
A Business in the Quickvee Pay Payments API represents a business entity who can send or receive ACH transfers. Each business is uniquely identified by a ksuid associated with the user, which is returned upon successful onboarding and is required for future operations such as linking bank accounts and initiating transfers.
Onboarding a business is a core part of working with the Quickvee Pay Payments API. This guide outlines the business onboarding workflow and provides context for common use cases.
A business is a specialized type of person in the Quickvee Pay Payments API. While the onboarding process is similar to that of a person, it includes additional fields and requirements. If you are transferring funds on behalf of a business entity, it must be onboarded using the business registration flow to meet compliance and regulatory obligations.
Testing
When testing in Quickvee Pay’s sandbox environment, you can create a business as usual. To include a bank account, simply use any random 12-digit account number along with one of our supported test routing numbers.
Step 1: Collect Business Information
To create a business we need to collect information about the point of contact and the information about the business itself. You can provide any combination of the following fields:
Point of Contact Information:
- First name (point of contact for the business)
- Last name (point of contact for the business)
- Phone
Business Information:
- Name (legal name of the business)
- Address (business address)
While only a bank account is required to create a business, we strongly recommend supplying full information to ensure a smooth onboarding experience and help meet regulatory and compliance standards.
Step 2: Provide a Bank Account
You can onboard a business with or without a connected bank account. If you choose to provide one, we support two methods:
Option A: Manual Entry
You can onboard a business using manually provided account details:
account_numberrouting_numberaccount_nameaccount_type(checkingorsavings)
Example
curl --location '{base}/api/v1/m/businesses' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: {sha256(API_KEY)}' \
--header 'X-Timestamp: {current_unix_timestamp}' \
--header 'X-Nonce: {unique_random_string}' \
--header 'X-Signature: {hex_encoded_signature}' \
--data '{
"person": {
"first_name": "string",
"last_name": "string",
"email": "string",
"address": {
"line_1": "string",
"line_2": "string",
"city": "string",
"state": "string",
"zip": "string"
}
},
"business": {
"name": "string",
"trading_name": "string",
"address": {
"line_1": "string",
"line_2": "string",
"city": "string",
"state": "string",
"zip": "string"
}
},
"bank_account": {
"account_number": "9876543211",
"routing_number": "021000021",
"account_name": "string",
"account_type": "checking|savings"
}
}'
Option B: Link a Plaid Account (WIP)
If you're using Plaid for bank account linking, include the following fields:
bank_account.plaid.access_tokenbank_account.plaid.account_id
Real-Time Validation (Recommended)
To reduce fraud risk and ensure funds can be successfully routed, we recommend enabling real-time bank account validation during onboarding. This feature is powered by our Account Intelligence product, which provides intelligent validation of routing and account numbers at the time of submission.
This validation step confirms that the provided routing and account numbers are both valid and correctly formatted. If name_match is enabled, it also checks that the account holder’s name aligns with the expected identity. In addition to these checks, the response includes a Risk Score and a set of decisioning insights that explain how the account was evaluated.
Although optional, enabling this validation is strongly recommended for all production integrations to reduce failure rates and improve payout reliability.
Next Up
Read Onboard a Person
Questions?
If you're encountering any issues, please reach out to support@quickveepay.com.