> ## Documentation Index
> Fetch the complete documentation index at: https://developers.dwolla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer Types

> Understanding and selecting the appropriate Customer type is the first step to a successful payment integration.

## Overview

A Dwolla API Customer is created programmatically by your CIP verified Dwolla Master Account via the [Create a Customer](/docs/api-reference/customers/create-a-customer) endpoint. All of the Customer's required information will be handled through the API and the Customer will interact directly with your application to manage their account. As a developer, you will want to create the Customer type that best suits the business case of your application. Below is a very high level detailing of the Customer types available with Dwolla.

<Note>
  Regardless of which Customer type(s) you choose to create for your
  application, keep in mind that all users onboarded as Customers must be US
  persons of age 18 or older.
</Note>

#### Customer types reference

| **Customer Type**              | CIP Verification | Dwolla `balance` | Default Transaction Send Limit | Transact with                             |
| ------------------------------ | ---------------- | ---------------- | ------------------------------ | ----------------------------------------- |
| **Personal verified Customer** | Yes              | Yes              | \$10,000 per **transfer**      | All Customer types                        |
| **Business verified Customer** | Yes              | Yes              | \$10,000 per **transfer**      | All Customer type                         |
| **Unverified Customer**        | No               | No               | \$5,000 per **week**           | Verified Customers, Dwolla Master Account |
| **Receive-only User**          | No               | No               | N/A                            | Verified Customers, Dwolla Master Account |

<Note>
  * The transaction send limits can be customized. <a href="https://www.dwolla.com/contact?b=apidocs">Contact Sales</a> for more information. <br />
  * By default, there is no limit for receiving funds.
</Note>

As you decide what type of customer to create for your application, a good thing to keep in mind is [Customer Identification Program (CIP) Verification](https://www.dwolla.com/updates/guide-customer-identification-program-payments-api). Remember that regardless of your application type, a transfer between two parties requires that at least one party must be CIP verified. It is your decision about which party completes this process based on your business model. Your own Dwolla Master Account can count as a verified party. You may also consider having both parties complete CIP verification, as we also require CIP verification in order for a customer to hold funds in the Dwolla network in the form of a balance.

## Verified Customer

Verified Customers are defined by their ability to both send and receive money. They can also interact with any customer type and hold a `balance` funding source within the Dwolla network. Think of the Dwolla `balance` as a wallet which a Customer can hold, send or receive funds to within the Dwolla network.

There are two types of verified Customer types your Customer can sign up as: `Personal` or `Business`.

### Personal Verified Customer

Personal Verified Customers can be used in any funds flows, as they can both send and receive funds. This Customer type can also hold a balance. The individual being onboarded as a personal Verified Customer will need to complete the identity verification process prior to being able to send or receive funds from/to their bank account. CIP verification involves passing Customer data to verify them, including their name, date of birth, and last four digits of their social security number. For more information about verifying this Customer type in our [Customer verification guide](/docs/personal-verified-customer).

With a per-transaction default send limit of \$10,000, this Customer type is able to interact with Dwolla and your application seamlessly.

### Business Verified Customer

Business Verified Customers are unique in their sign up flow, as they need multiple parties to be verified. These will include:

* The Business (required)
* The Controller (Conditionally Required)
* The Beneficial Owner (Conditionally Required)

Business Verified Customers will need an Account Admin to sign up the company during the onboarding process. This Account Admin is not identity verified. To become a fully verified Customer, a controller and/or a beneficial owner may need to be identity verified. A controller is any natural individual who holds significant responsibilities to control, manage, or direct a company or other corporate entity (i.e. CEO, CFO, General Partner, President, etc). A company may have more than one controller, but only one controller's information must be collected. A beneficial owner is any natural person who, directly or indirectly, owns 25% or more of the equity interests of the company.

The Controller will need to provide information to be fully identity verified. This includes their last four SSN and date of birth for identity verification purposes. For certain business types, a business' EIN will also need to be provided as part of the CIP process. For more information about adding a controller, check out our [business verified Customer creation guide](/docs/business-verified-customer).

Certain business types may also need to add and certify beneficial ownership. You can find more information about adding beneficial owners in our [developer resource article](/docs/business-verified-customer#step-3-adding-beneficial-owners). To learn more about certifying beneficial ownership, reference the [certify beneficial ownership](/docs/business-verified-customer#step-4-certify-beneficial-ownership) section in the business verified customer guide.

For a full series of steps that goes in depth on business verified Customers, take a look at our [Customer verification guide](/docs/business-verified-customer). This guide also goes into detail on the identity verification process for controllers and beneficial owners.

## Unverified Customer

An unverified Customer type requires a minimal amount of information : `firstName`, `lastName` `email`, and optionally `businessName` for businesses. While Customer creation and onboarding is light weight compared to a verified Customer, there are a few things to consider when choosing this customer type.

Unverified Customers have a default transaction send limit of `$5000` per week. A week is defined as Monday to Sunday UTC time. If you have an unverified Customer looking to send more than `$5,000` in a week, you may want to explore [upgrading them to a verifed Customer type](/docs/api-reference/customers/update-a-customer) or [contacting sales](https://www.dwolla.com/contact?b=apidocs) for more information about customizing the send limit.

As this Customer is not CIP verified, they will only be able to transact with verified Customers or your Dwolla Master Account.

## Receive-only User

Receive-only Users are restricted to payouts only funds flow. This user type maintains limited functionality in the API and is only eligible to receive transfers to an attached bank account. This user type can only interact with verified Customers and a Dwolla Master Account.

<Note>
  Receive-only Users cannot send funds back. If you need this user to send funds
  back for any reason, you may need to resolve this outside of the Dwolla
  network.
</Note>