By Marcus Bennett, payment onboarding specialist with 8 years of merchant-risk operations experience
Last reviewed: July 30, 2026
Finix reviews a business before enabling it to process payments or receive merchant settlements. An application may show PROVISIONING, UPDATE_REQUESTED, APPROVED or REJECTED, and each status requires a different response. This independent guide is not affiliated with or operated by Finix.
Start with the status displayed in the Finix Dashboard. Do not submit a second application merely because the first review has not finished; duplicate merchant records can make the account harder to trace.
What Finix merchant verification checks
Finix provides payment processing and embedded-payment infrastructure to merchants, software companies and marketplaces. Platforms can onboard their sellers through a Finix-hosted Onboarding Form or build their own flow with Finix APIs. Both methods ultimately send seller information into the same underwriting process.
Finix collects information concerning the business, its ownership, expected processing activity and the bank account intended for payouts. Its documentation says the review includes the seller’s control owner and any beneficial owner holding at least 25 percent of the business.
The review is not limited to confirming that a company exists. Payment underwriting also evaluates fraud exposure, financial risk, compliance concerns and whether the business falls within Finix’s supported activity rules.
A normal application can therefore involve several checks:
| Review area | What Finix may need to establish |
|---|---|
| Business identity | The legal entity and operating information are consistent |
| Control person | The person submitting or controlling the business can be identified |
| Beneficial ownership | Required owners are listed and can be reviewed |
| Bank account | The account exists and belongs to the appropriate party |
| Processing profile | Expected sales activity fits the stated business |
| Industry eligibility | The activity is not prohibited and can meet any enhanced review |
| Risk | The projected fraud, dispute and financial exposure is acceptable |
Finix’s process reflects broader financial-sector customer-due-diligence practices. FinCEN’s Customer Due Diligence Rule requires covered financial institutions to identify and verify qualifying beneficial owners of legal-entity customers, subject to exclusions and updated relief issued in 2026.
Finix is not saying that every merchant is a bank customer under precisely the same rule. Its banking and processing relationships create an underwriting environment in which ownership and identity information must be evaluated.
What each onboarding status means
The status is the useful part.
A newly submitted merchant normally moves into PROVISIONING while Finix reviews the application. An account that passes the review moves to APPROVED. If Finix needs corrected data or supporting documentation, the merchant moves to UPDATE_REQUESTED. A business Finix cannot onboard following its risk decision moves to REJECTED.
| Finix status | Practical meaning | Appropriate action |
PROVISIONING | Review is in progress | Monitor the application and notifications |
UPDATE_REQUESTED | Finix needs a correction or document | Open the stated remediation request |
APPROVED | Merchant underwriting was successful | Confirm processing and payout configuration |
REJECTED | Finix declined the merchant under its risk review | Read the available outcome information and contact the platform or Finix support |
Do not treat UPDATE_REQUESTED as a rejection. Finix automatically sends the application back for review after the requested updates have been submitted.
Nor does PROVISIONING mean the account has permission to process live payments. It indicates that the review is active.
Why Finix requests an update
Finix documents two broad reasons for an update request: information cannot be verified, or submitted data is invalid. One official example is a bank account whose owner cannot be identified. Another is a routing number that does not belong to a financial institution.
Other remediation may concern identity information, business records or ownership details. Finix’s documentation gives a concrete identity-verification instruction: the verification should match the owner’s full name, remain readable and not be expired.
The platform administrator can find affected merchants under Merchants > Merchant Accounts and open the Update Requested tab. The merchant detail page shows the requested documents or data changes and may include a note explaining what failed.
Read that note first. Skip random edits to fields Finix did not flag.
When the seller originally used a hosted Onboarding Form, the platform can use Share Onboarding Form Link to return the seller to the same application. The form highlights fields requiring correction and displays upload controls for requested documents.
After resubmission, the status returns to PROVISIONING, and Finix creates a new verification automatically. The platform does not need to create another merchant merely to restart review.
Why bank-account verification can fail
The payout account is part of merchant underwriting because Finix needs to know where settlement funds will be delivered and whether the account belongs to the appropriate business or owner.
A typed account can fail review when the routing information is invalid or ownership cannot be matched. Finix also supports Plaid inside its no-code Onboarding Forms, allowing a seller to connect an account through a bank-authentication flow rather than relying entirely on manually entered information.
Finix says Plaid can verify both the existence and ownership of a connected bank account during onboarding. Availability can vary according to the platform’s integration and account configuration.
That verification does not guarantee that every future payout will succeed.
A deposit may later be returned if the saved account has closed, does not accept the transfer or contains incorrect information. Finix also reviews changes to an existing payout bank account, so replacing the account may not take effect immediately.
Confirm the destination before the first live settlement. Skip repeated bank-account changes while a review is already pending unless the displayed request specifically calls for one.
Why a Finix merchant can be rejected
Finix says seller rejections can result from fraud risk, financial risk or other compliance reasons. The merchant’s status moves to REJECTED when Finix cannot approve it under the underwriting decision.
A rejection is not necessarily evidence that the company is illegal or fraudulent. Payment processors evaluate whether a business fits their own risk appetite, banking relationships, network requirements and operational capabilities.
Finix maintains a published list of prohibited and restricted activities. Prohibited businesses are unsupported, while restricted businesses require enhanced due diligence. The company says those classifications consider legal requirements, financial-partner restrictions, card-network rules, dispute exposure and reputational risk.
Its current policy also states that businesses using the covered services must operate and maintain a physical presence in the United States, excluding U.S. territories. The list is not exhaustive and may be changed.
That geographic condition is easy to overlook.
A U.S.-registered company with operations conducted entirely elsewhere may receive a different risk outcome from a company with an operating presence that matches its application. Business eligibility also varies by region and product.
Finix does not publish a universal appeal process promising reconsideration after every rejection. A platform merchant should review the outcome information available in the Dashboard and contact the software platform that initiated the onboarding. Direct Finix customers can use the official support channel documented by Finix.
Approval does not guarantee immediate payouts
Merchant approval authorizes the account under the completed underwriting decision. It does not promise that every settlement will be released without further review.
Finix groups processed transactions into settlements. Under its managed settlement flow, Finix reviews and approves those settlements automatically, but transactions or entries flagged for risk can cause a settlement to be held for additional review. Finix says its team opens a support ticket when more investigation is needed.
This distinction matters after a merchant’s first busy sales period.
An APPROVED onboarding status and a held settlement can exist at the same time. One concerns permission to operate; the other concerns a specific group of funds.
Finix’s terms place reconciliation responsibility on the merchant. The May 4, 2026 terms say merchants must compare Dashboard information with their transaction records and promptly report errors. The terms describe a 60-day reporting window for an error first shown in the Dashboard, after which related monetary claims may be waived under the agreement.
Inspect settlements regularly. Do not wait until several payout cycles have passed before questioning an unexplained balance.
A held settlement can be associated with risk review, unusually changed processing activity or flagged transactions. The public documentation does not publish one maximum review period applying to every case.
How platforms monitor merchant applications
Finix supports Dashboard and email notifications for five onboarding events:
- Onboarding Form submitted
- Merchant approved
- Merchant rejected
- Merchant updates requested
- Merchant updates submitted
The notification controls are documented under Settings > User > Notification Settings. Each lifecycle event can be enabled separately.
Platforms using an API integration can also receive onboarding webhooks. This prevents staff from repeatedly opening every merchant record to look for a status change.
A practical merchant-operations workflow is to separate applications into three queues: active review, update required and final decision. Mixing PROVISIONING accounts with merchants awaiting documents makes follow-up less reliable.
Finix’s hosted form cannot simply be deleted after creation, according to its documentation. Platforms should therefore manage the form links and associated merchant records carefully rather than creating replacements for every correction.
Small detail. Large cleanup later.
What to do when onboarding appears stuck
Check the merchant’s Onboarding State before contacting support.
If the status is UPDATE_REQUESTED, open the merchant detail page and address only the listed remediation items. If it is PROVISIONING, confirm that the latest requested submission was completed and that no new notification appeared. For REJECTED, review the outcome information rather than resending the identical application.
A platform using a white-labeled seller experience may control the invitation and merchant communication. In that case, the seller should contact the platform first because its administrators can access the merchant record and share the original Onboarding Form link.
Finix advertises emergency support availability around the clock, while its documentation routes ordinary technical and payment questions through its support team.
Do not send confidential onboarding information through an unverified contact form, social-media account or search-result phone number. Use the support route linked from the authenticated platform or Finix’s official documentation.
Finix onboarding FAQ
How long does Finix verification take?
Finix does not publish one approval deadline for every merchant.
A hosted form may be completed in minutes, but completing the form and passing underwriting are separate events. Review time depends on whether submitted information can be verified and whether Finix requests corrections or enhanced due diligence.
What does UPDATE_REQUESTED mean?
Finix needs corrected information or documentation before it can continue. The account is not yet rejected.
Can I edit a submitted Finix application?
Yes, when Finix requests an update. A platform can edit the affected merchant data in the Dashboard or return the seller to the original Onboarding Form using the sharing control.
Why does Finix review business owners?
Finix collects the control owner and qualifying beneficial owners as part of seller underwriting and identity verification. Its documentation applies a 25 percent ownership threshold when identifying beneficial owners for onboarding.
Can a rejected account be submitted again?
Do not create a duplicate immediately. Review the stated outcome and use the platform or Finix support route to determine whether corrected circumstances can be reconsidered. Finix does not publish a promise that every rejection can be reversed.
Does merchant approval mean settlements cannot be held?
No. Approved merchants can still have particular settlements held for risk review when transactions or settlement entries are flagged.
Why does the bank account need separate verification?
The account is used for merchant payouts, so Finix may need to confirm that it exists and is associated with the correct party. Invalid routing details or an ownership mismatch can trigger an update request.
Use the merchant’s current onboarding state as the decision point. Correct an identified update request, wait on an active review, or escalate a rejection through the verified platform channel without opening duplicate merchant records.