By Olivia Hart, payment onboarding specialist with 9 years of experience supporting business verification and ACH account setup
Last reviewed: July 21, 2026
Dwolla provides bank-payment infrastructure that platforms use to create customer records, verify businesses, connect bank accounts and move money through ACH or supported real-time rails. A business customer may need to verify its company, controller and beneficial owners before it can use the intended payment features.
This independent guide is not affiliated with Dwolla.
Most onboarding delays begin with a category mistake. The applicant assumes that creating a business record, confirming a bank account and becoming eligible to send payments are one step. Dwolla treats them as separate processes, and each can have its own status.
What is a Dwolla business customer?
Within a Dwolla integration, a customer is an individual or business that the platform intends to transact with. Customer records are created and managed programmatically by the Dwolla client rather than necessarily being opened through a public consumer signup page.
A business verified customer is designed for a legal entity that needs broader payment capabilities than a basic customer record. Dwolla’s documentation says business onboarding begins with an account administrator, but that administrator is not automatically the person whose identity satisfies the company’s verification requirements. A controller and, for certain business structures, beneficial owners may also need to be identified and verified.
That distinction catches teams off guard.
The person completing the application might be an employee, operations manager or developer. Dwolla may still require details about a senior individual who controls or directs the company and about people who meet the applicable ownership threshold.
Who is the controller?
Dwolla describes a controller as a natural person with significant responsibility for managing or directing the company. Examples in its customer-type documentation include a chief executive, chief financial officer, president or general partner.
The controller is not always the person with the largest equity stake. The role concerns control or management responsibility.
This is one reason a business can enter apparently accurate company information yet remain incomplete. The organization has been identified, but the person entered as controller may not match the role required for that record.
Choose the controller carefully. Skip the habit of entering whichever employee happens to be completing the form.
The company’s onboarding interface should explain the role in plain language before asking for information. A vague field titled “business contact” is not enough because an ordinary contact and a controller serve different purposes.
Who counts as a beneficial owner?
Dwolla’s API documentation defines a beneficial owner for this process as an individual who owns 25% or more of the company’s equity. Business verified customers organized as corporations, limited liability companies or partnerships may be required to identify beneficial owners in addition to the controller.
The broader regulatory background comes from customer due diligence requirements administered by the Financial Crimes Enforcement Network, or FinCEN. FinCEN describes the framework as requiring covered financial institutions to identify individuals who own at least 25% of a legal entity and one individual who controls it, subject to the applicable rules and relief.
Not every company has four owners with equal shares. Some have one majority owner, several qualifying owners or no individual meeting the ownership threshold. The controller requirement remains important even where no person reaches 25%.
Dwolla also notes that customers themselves must be U.S. persons, while a business verified customer may have a controller or beneficial owner outside the United States.
The exact onboarding path can vary by business structure. Do not infer an exemption from a company name or tax classification alone.
What information must be verified?
The Dwolla integration collects company and identity information required for the relevant customer type. For beneficial owners, the API documentation describes personal information, an address and identifying information used for identity verification.
Sensitive information should be collected only through the authorized application flow. It should never be requested through an unsolicited email, public support thread or ordinary chat message.
Businesses implementing Dwolla also need to distinguish among three records:
- The legal business
- The controller
- Each required beneficial owner
An error attached to one record should not be displayed as a generic “company verification failed” message. The user needs to know which person or organization requires another action, without exposing private details unnecessarily.
A well-built interface might say that the business record needs supporting documentation or that an owner must complete another verification step. It should not tell the user to recreate the entire account unless the underlying workflow requires that action.
What do the verification statuses mean?
Dwolla business customers can move through statuses such as retry, document, verified, suspended or deactivated. Beneficial owners have verification states that include verified, document and incomplete.
Those labels lead to different actions.
A retry state generally means information needs to be corrected and submitted again through the available update path. A document state means identity or business documentation is required for manual review. Verified indicates that the applicable verification step has been completed.
Incomplete is not the same as rejected forever. Dwolla’s business-verification guide explains that a beneficial owner in incomplete or document status can restrict the business customer’s ability to send or receive funds until the issue is resolved.
Read the available action link. Do not guess.
Dwolla uses links on customer and beneficial-owner resources to show the actions currently permitted. An integration should rely on those links and webhook events rather than hard-code one recovery path for every failed check.
Why does Dwolla request documents?
A customer or beneficial owner may enter document status when automated verification cannot complete the identity check. Dwolla’s document documentation states that verified personal or business customers in this state may need color images of identifying documents for manual review.
For a beneficial owner, document upload is required when that owner has a document verification status. The integration can use Dwolla’s document-upload endpoint or an appropriate embedded component to collect the required material through the authorized workflow.
Dwolla says document review may take roughly one to two business days before approval or rejection. Its events documentation also provides notifications when a beneficial-owner verification document is approved or rejected.
That time frame is not a guarantee for every case. Document quality, missing information and additional review can affect the outcome.
Upload once through the proper screen. Skip repeated submissions unless the application reports a rejection or requests a replacement.
Why can’t the business send funds yet?
A company may have created its customer record while its beneficial ownership remains uncertified.
Dwolla provides a separate beneficial-ownership certification status with values including uncertified, certified and recertify. The certification confirms that the submitted owner information is accurate and complete, and it affects whether the business can send funds.
This creates a common operational friction: all individual owners appear verified, but the final certification step has not occurred.
Verification and certification are related, not identical. Each owner may need to reach an acceptable status, after which the business or platform certifies the ownership information as complete.
A recertify status signals that the ownership information needs certification again. The integration should surface that action rather than allowing payment attempts to fail without an explanation.
Check certification first when a verified-looking business cannot send money.
Is bank verification part of business verification?
No. Identity verification and bank-account verification solve different problems.
Business verification establishes the legal entity and the relevant people behind it. Bank verification confirms the funding source used to send or receive payments. Dwolla supports instant bank verification and micro-deposits, and its documentation says payments initiate on verified accounts.
Micro-deposit verification uses two small amounts that generally appear in the bank account within one to two business days. The customer then confirms those amounts through the application that started the verification.
A business can therefore be identity verified but unable to transact because its bank account is not ready. The reverse can also occur: a bank connection exists, but company or owner verification remains incomplete.
Display both statuses.
“Account connected” should not be used as a substitute for “business verified” or “bank verified.”
How should verification errors be handled?
Dwolla returns structured API errors, including HTTP status information, Dwolla error codes and embedded errors where a request contains several validation problems.
The platform should store the original error internally and present a narrower customer-facing instruction. A misspelled field, a retry state and a document request should not all produce the same message.
Webhook events matter here. Dwolla publishes events for changes in customer, beneficial-owner and document statuses, allowing the client to update onboarding screens after an asynchronous review.
The experienced implementation detail is simple: do not mark onboarding “failed” merely because the initial API response was not verified. Some cases move into document review and finish later.
The customer record should remain traceable throughout that process. Support agents need to see which record is waiting, what action is available and whether a document review has already started.
How much does Dwolla cost?
Dwolla currently presents custom pricing based on transaction volume, payment rails and integration requirements. It does not advertise one fixed tier that applies to every business.
Verification work should be included in the operational cost assessment. A company needs to account for engineering, customer support, document exceptions, bank verification and payment reconciliation, not only the quoted transfer price.
A business expecting complicated ownership structures or frequent document reviews should discuss that onboarding model during the commercial evaluation. Generic transaction volume alone will not describe the full workload.
Frequently asked questions
Does every owner need verification?
Only owners required by the applicable business structure and verification flow.
Is the account administrator automatically the controller?
No. Dwolla states that the account administrator is not identity verified merely by signing up the company. A controller or beneficial owner may need separate verification.
What ownership percentage does Dwolla use?
Dwolla’s beneficial-owner documentation identifies individuals owning 25% or more of company equity.
Why does the customer show document status?
Automated verification did not complete, so an identifying document may be required for manual review. Dwolla says reviews commonly take one to two business days.
Can the business transact before ownership certification?
The certification status affects the business customer’s ability to send funds. Complete verification and certify the beneficial-owner information through the available workflow.
Is beneficial-owner verification the same as bank verification?
No. One verifies people behind the business; the other verifies the payment account.
Can a non-U.S. person be a beneficial owner?
Dwolla says customers must be U.S. persons, but business verified customers may have non-U.S. controllers or beneficial owners.
Where should a client get onboarding help?
Dwolla maintains a support portal for clients. Its published instructions direct users who need portal setup or login assistance to the official support channel.
