By Lauren Pierce, merchant-onboarding analyst with 9 years of KYC, KYB and payment-underwriting experience
Last reviewed: July 30, 2026
Finix verifies the business, its control person, qualifying beneficial owners, payout bank account and expected payment activity before a seller can begin processing. If information is invalid or cannot be confirmed, the Merchant moves to UPDATE_REQUESTED until the seller corrects the data or supplies the requested document. This independent guide is not operated by or affiliated with Finix.
Creating a Merchant resource is not approval. The seller can accept live payments only after the Finix onboarding state becomes APPROVED.
What Finix checks during onboarding
Finix onboarding combines identity verification, business verification and payment-risk underwriting.
The platform collects information in four broad areas:
| Information group | Examples |
|---|---|
| Business information | Legal name, entity type and business address |
| Owner information | Control person and qualifying beneficial owners |
| Processing information | Expected volume and payment activity |
| Bank information | Account used for seller payouts |
Finix describes its review as including Know Your Customer and Know Your Business checks. KYC verifies the people controlling the account, while KYB verifies the legal business and related registration information. Finix also supports sanctions and compliance screening as part of its merchant-underwriting tools.
Underwriting is not limited to checking whether the company exists.
The review can also consider the merchant’s business model, financial risk, fraud exposure, expected transaction profile and whether Finix can support the seller’s activity. Finix says merchant applications can be rejected for financial risk, fraud risk or other compliance reasons.
A valid registration document therefore does not guarantee approval.
Who is the control owner?
Finix collects details about one control owner for the seller’s business. This is the person with significant responsibility for managing or directing the company.
Depending on the business, that person might be:
- Chief executive officer
- President
- Managing member
- General partner
- Treasurer
- Another senior person responsible for the entity
The control person is not necessarily the individual with the largest ownership percentage. A business can have a control person who owns little or none of the company but has substantial managerial authority.
Finix’s onboarding process verifies the control owner as part of customer identification. Its hosted Onboarding Forms also require a government-issued identity document and selfie photograph from merchants so Finix can confirm that the actual control owner is submitting the application.
Use the real controlling individual. Skip listing an employee merely because that person is completing the online form.
Which beneficial owners must be listed?
Finix requires details for each beneficial owner who owns at least 25% of the business. A separate Associated Identity must be created for every person meeting that threshold when onboarding through the API.
Consider these examples:
| Ownership structure | Finix owner records generally needed |
| One person owns 100% | That owner plus the required control-owner role |
| Two people own 50% each | Both beneficial owners |
| Four people own 25% each | All four beneficial owners |
| Five people own 20% each | No owner reaches the 25% beneficial-owner threshold, but a control person is still required |
| One company owns the applicant | The ownership structure may need to be traced to qualifying individuals |
The threshold is 25% or more, not greater than 25%.
A person holding exactly 25% should be included.
Do not split an owner into several incomplete records or omit someone because ownership is held indirectly. The legal ownership structure supplied during onboarding should match the company’s actual records.
Why does Finix request a government ID and selfie?
Finix says its hosted Onboarding Forms require government IDs and selfie photos to reduce identity theft and verify that the real control owner is submitting the application.
This verification can fail when:
- The ID is expired
- The image is blurred or cropped
- Information on the form differs from the document
- The selfie does not clearly show the applicant
- The document type is unsupported
- The owner’s name is entered incorrectly
- The submitting person is not the listed control owner
The photograph should be submitted only through the Finix-hosted onboarding workflow or another verified account channel.
Do not send identification through an unrelated email address or public file-sharing link. Finix provides hosted forms and authenticated document-upload workflows for this purpose.
A request for another ID does not necessarily mean Finix believes the seller committed fraud. It can simply mean the original image or data could not be verified.
What do Finix merchant states mean?
Finix uses four main onboarding states:
| Onboarding state | Meaning |
PROVISIONING | Application is being created or reviewed |
APPROVED | Merchant can begin accepting payments |
UPDATE_REQUESTED | Finix needs corrected data or documents |
REJECTED | Finix cannot approve the merchant as submitted |
Finix recommends using webhooks to monitor Merchant state changes rather than repeatedly checking the account manually.
PROVISIONING is not a failure.
It means the application has not reached a final state. The seller should avoid creating another Merchant merely because the first one remains under review. Multiple duplicate merchant records can make onboarding and reporting harder to reconcile.
APPROVED is the operational state that matters. Finix’s quickstart states that the Merchant is ready to process payments once approval is complete.
What does UPDATE_REQUESTED mean?
UPDATE_REQUESTED means Finix needs additional information before it can complete the review.
Finix gives two documented examples:
- It cannot identify the owner of the submitted bank account.
- The submitted routing number does not belong to a valid financial institution.
Other requests may concern identity, business or ownership information.
The Dashboard contains an Update Requested tab under the merchant-account area. Opening the merchant shows the requested data or documents and may include a note explaining the problem.
The request is not satisfied merely by acknowledging it.
The seller or platform must correct the highlighted information or upload the specific document requested. Once the form is resubmitted, Finix returns the Merchant to PROVISIONING and automatically creates another verification review.
The normal sequence is:
PROVISIONING → UPDATE_REQUESTED → corrected submission → PROVISIONING → final decision
That second PROVISIONING state is expected. It means Finix is reviewing the updated application.
How does the seller submit requested updates?
When the original application used a Finix Onboarding Form, the platform can reopen the same form for the seller.
Finix documents this process:
- Open the affected Merchant.
- Select the option to share or retrieve the Onboarding Form link.
- Send the original form link to the seller.
- Have the seller open the form.
- Correct fields highlighted in red.
- Upload documents shown in the requested-file areas.
- Resubmit the form.
The same link can therefore be used for corrections. The platform does not need to create a new seller account.
A platform can also make changes directly through the Dashboard when it already possesses the correct data or document. Finix recommends using Onboarding Forms for a more streamlined seller experience but permits Dashboard updates for flexibility.
Use one route consistently. Skip editing the Dashboard while the seller simultaneously changes the form, because conflicting updates can create additional review questions.
How are documents uploaded?
Finix supports document uploads through both the Dashboard and Files API.
The documented Dashboard route is:
- Open the seller’s Identity page.
- Select the Files tab.
- Choose Upload File.
- Upload the requested record.
- Confirm the successful-upload banner.
API integrations first create a File resource associated with the merchant, then upload the file directly or generate an external link that lets the seller upload from a browser.
Typical verification records can include:
- Government identity document
- Business-registration record
- Bank-account evidence
- Ownership documentation
- Information requested in the Merchant outcome code
Submit the exact requested record.
A random bank statement does not resolve an invalid legal name. A formation certificate does not prove ownership of the payout bank account unless it contains the information Finix requested.
Why is the bank account being reviewed?
Finix collects a bank-account Payment Instrument during seller onboarding so it can send settlement payouts after approval.
The account may require clarification when:
- The account owner cannot be identified
- The legal name does not correspond with the seller
- The routing number is invalid
- Required bank fields are incomplete
- The account type is unsupported
- The banking data contains a typing error
Finix specifically identifies inability to verify the bank-account owner and an invalid routing number as reasons for an update request.
Do not replace the bank account repeatedly without reading the outcome note.
When ownership is the problem, another account with the same unexplained name can produce the same result. The seller may need evidence connecting the bank account to the legal business or verified owner.
The payout destination should belong to the seller or otherwise satisfy the processor’s documented requirements.
What information must an API onboarding flow collect?
Finix’s seller-onboarding API guide outlines five major steps:
- Collect seller information and consent.
- Create an Identity.
- Create a bank-account Payment Instrument.
- Create the Merchant.
- Listen for Merchant review updates.
The seller must also explicitly agree to both the platform’s terms and the applicable Finix Terms of Service through a click-through agreement. Finix supplies required consent language and notes that the correct terms version depends on the seller’s country and processor.
A checkbox that is selected by default is weaker evidence than an affirmative action taken by the seller.
The integration should retain:
- Consent timestamp
- Terms version
- Seller Identity ID
- Associated owner identities
- Bank Payment Instrument ID
- Merchant ID
- Current onboarding state
- Update-request outcome codes
These records make it possible to explain whether an application is incomplete, under review or rejected.
Why was a Finix seller rejected?
Finix says sellers can be rejected because of financial risk, fraud risk or other compliance reasons. When rejection occurs, the Merchant moves to REJECTED, and outcome codes are available in the Dashboard or API.
A rejection differs from an update request:
UPDATE_REQUESTED | REJECTED |
| Application requires more information | Finix reached an adverse decision |
| Seller can submit requested corrections | Resubmission may not be available through the normal flow |
| Merchant returns to review after update | Platform should review outcome codes and contact its Finix representative when appropriate |
| Not a final approval decision | Final onboarding state unless Finix advises otherwise |
Do not tell the seller to create another company spelling or another Finix account to bypass rejection.
If the platform believes the decision resulted from incorrect information, it should review the outcome codes and contact its authorized Finix point of contact. Finix’s rejection guide directs platforms to that route for additional information or suspected errors.
Submitting altered information to avoid underwriting can create a larger compliance problem.
How long does Finix approval take?
Finix’s current merchant-account guide says automated KYC and KYB workflows help most merchants move from application to payment acceptance within one business day.
That is a typical product claim, not a guaranteed approval deadline for every seller.
Applications requiring documents, manual review or risk analysis can take longer. Approval speed can depend on:
- Data accuracy
- Identity-verification results
- Ownership complexity
- Bank-account verification
- Industry
- Expected processing activity
- Additional documents
- Finix or sponsor-bank review
Avoid promising a seller that the account will be active at a specific hour.
The dependable status is the Merchant’s current onboarding_state. When it becomes APPROVED, the seller can begin processing under the approved configuration.
How should platforms monitor onboarding?
Finix offers email and Dashboard notifications for:
- Onboarding Form submitted
- Merchant approved
- Merchant rejected
- Merchant updates requested
- Merchant updates submitted
Users can subscribe under:
Settings > User > Notification Settings
API-based platforms should also subscribe to Merchant webhooks. Finix documents merchant.updated for onboarding changes and merchant.underwritten when the Merchant is approved and ready to accept payments.
The platform should not activate payment acceptance based only on form submission.
A safer workflow is:
- Seller submits onboarding form.
- Platform records the Merchant ID.
- Finix reviews the application.
- Platform handles any update request.
- Webhook reports approval.
- Platform fetches the Merchant to confirm state.
- Payment features are enabled for the seller.
The webhook is the notification. The fetched Merchant state is the current record.
Finix merchant-verification FAQ
Why does Finix need my personal information?
Finix must verify the individuals controlling or owning the business as part of merchant identification and underwriting.
Which owners must be listed?
Finix requires the control person and each beneficial owner with at least 25% ownership.
Why is Finix asking for a selfie?
Finix requires identity documents and selfie photos in its hosted Onboarding Forms to confirm that the actual control owner is submitting the application.
What does UPDATE_REQUESTED mean?
Finix needs corrected information or another verification document before it can finish underwriting.
Do I need to create a new onboarding form?
No. A seller can use the original Onboarding Form link to correct highlighted fields and upload requested documents.
Can I process payments while the state is PROVISIONING?
The Merchant is ready to process after the onboarding state becomes APPROVED.
Why was my bank account rejected?
Finix may be unable to identify the account owner, or the submitted routing number may be invalid. Review the exact update-request note before replacing the account.
Is Finix approval a hard credit check?
Finix says it does not conduct hard credit checks on sellers as part of the described onboarding process.
Can a rejected seller apply again?
Do not create a duplicate account automatically. Review the rejection outcome codes and contact the platform’s Finix representative when the decision may be based on incorrect information.
List the real control person, include every owner at or above the 25% threshold and make the legal business, bank account and supporting documents consistent. When Finix requests an update, correct the existing Merchant application rather than starting another one.