By Noah Bennett, merchant risk operations analyst with 8 years of payment-support experience
Last reviewed: July 30, 2026
Finix is a business payment processor used to accept online and in-person payments, manage transactions, send payouts, and embed payment services into software. Authorized company users enter the Finix Dashboard, while buyers normally deal with the merchant that sold the product or service.
This independent guide is not affiliated with Finix Payments, Inc. Buyers should contact the seller about purchases, cancellations, or refund requests; merchants should use Finix’s documented dashboard and support routes for processing or account problems.
What is Finix?
Finix provides payment technology for direct merchants, software platforms, marketplaces, and businesses that send funds to recipients. Its system covers payment acceptance, transaction operations, merchant administration, settlements, payouts, refunds, and chargeback management.
The user’s role determines what Finix page is relevant.
A merchant employee may need the business dashboard. A developer may need API credentials. A buyer who paid through a Finix-powered checkout usually needs the merchant’s customer-service channel instead.
That buyer does not normally receive access to the merchant’s Finix account.
Contact the seller first for an unrecognized order, delayed service, cancellation, duplicate purchase, or refund request. The issuing bank becomes relevant when the cardholder decides to challenge a charge formally.
Where is the Finix login?
Finix publishes a business login from its official website. The dashboard is intended for authorized owners, administrators, developers, and other team members working with a Finix merchant or platform account.
After signing in, confirm four details:
- The correct organization is open.
- The intended sandbox or live environment is selected.
- The user has the necessary role.
- Multi-factor authentication has been completed.
Finix supports MFA through SMS or a mobile authenticator. Administrators and User Management Admins can enforce MFA from Company > Team > Members and can reset it for an individual member from that same team-management area.
A password reset may not help when the failure occurs at the MFA stage. Ask an authorized administrator to review the user record and reset the second-factor enrollment when appropriate.
Do that first. Skip duplicate user accounts.
Dashboard access is different from API authentication
A dashboard login belongs to a person using the web application. Finix API requests use HTTP Basic Authentication with an API username-and-password combination.
These are separate problems:
- Dashboard does not open: check the user, organization, role, and MFA.
- API request returns an authentication error: check the API credentials and environment.
- Transactions appear missing: confirm sandbox versus live.
- A refund control is unavailable: check permissions and payment status.
- A dispute cannot be submitted: check the response state and deadline.
Finix represents payment activity through resources such as Transfers and Authorizations. A Transfer can represent several forms of money movement, including a card payment, bank credit, refund, reversal, or merchant payout.
That structure explains why a user may see related records under Transactions rather than one simple “payment” object for every event.
How Finix refunds work
Finix permits merchants to issue either full or partial refunds after a payment has been processed. Refunds can be initiated through the Dashboard, API, or directly through a supported payment terminal.
The merchant initiates the refund.
A buyer cannot normally enter Finix and independently reverse a merchant transaction. The buyer asks the seller, and an authorized merchant user decides whether the request qualifies under the seller’s terms.
A full refund returns the entire eligible transaction amount. A partial refund returns only a selected portion. The amount available can depend on the original payment and any refunds that have already been issued.
Finix records refunds as money movements associated with the payment. That means the refund may appear as a related Transfer rather than replacing or deleting the original sale record.
Keep both records. The original payment and subsequent refund are separate events needed for reconciliation.
Refund versus void
A refund occurs after a payment has been processed. A void generally cancels an authorization before it is captured and settled.
The distinction matters because a pending authorization is not the same as a completed sale. When an authorization has not yet been captured, voiding it may be the appropriate action rather than creating a refund.
Once a payment has completed, use the documented refund workflow.
This is a frequent operations mistake. A team sees a customer’s pending card entry and assumes a refund must be sent, even though the transaction may still be an uncaptured authorization.
Check the transaction state before choosing the action.
Refund versus dispute
A refund is initiated by the merchant. A dispute, also called a chargeback, begins when the cardholder challenges a payment through the issuing bank.
| Process | Who starts it | Where it begins |
|---|---|---|
| Refund | Merchant | Finix Dashboard, API, or supported terminal |
| Dispute | Cardholder | Card-issuing bank |
| Dispute response | Merchant | Finix Dashboard or API |
A buyer should generally ask the merchant to correct the problem before filing a bank dispute. A merchant that has already issued a refund should retain the related transaction record in case a dispute is later opened.
Refunding a transaction does not necessarily erase every processing cost or operational consequence. The merchant’s agreement and product-specific pricing control the actual financial treatment.
What happens after a buyer files a dispute?
Finix documents a standard dispute lifecycle.
The cardholder challenges the charge with the issuing bank. The bank reverses the payment and debits Finix. Finix then creates a Dispute record, debits the merchant through a settlement, and alerts the merchant through the Dashboard and a configured webhook.
The merchant can then accept the dispute or submit evidence.
Finix says dispute cases generally take around two to three months from beginning to end. In rare cases, the process may take as long as six months. Accepting the dispute can end the case sooner, but there is no dependable way to accelerate a contested review by the issuing bank.
Do not promise a quick result.
The merchant does not make the final decision after evidence is submitted. The issuing bank evaluates the case under the applicable card-network process.
How merchants respond to a Finix dispute
Finix allows merchants to monitor disputes through the Dashboard or API. The merchant can review the dispute state, accept the case, or provide evidence supporting the transaction.
The exact response should match the reason for the dispute. Relevant business records may include the order details, acceptance of terms, delivery information, cancellation history, customer communications, or proof that the service was provided.
Prioritize the deadline. Skip unrelated dashboard work until the dispute response has been completed.
Finix’s API supports uploading, retrieving, updating, and deleting dispute-evidence records. The Dashboard provides the operational interface for businesses that do not manage the response entirely through an integration.
A late or incomplete response can reduce the merchant’s chance of recovering the disputed funds.
Who should solve each Finix problem?
The merchant, Finix, and the issuing bank have different responsibilities.
Contact the merchant
A buyer should contact the seller about:
- A product or service not received
- Cancellation
- A duplicate order
- A refund request
- Subscription questions
- Recognition of the merchant name
Contact Finix
An authorized business user may need Finix assistance for:
- Dashboard or product problems
- Technical integration issues
- Merchant-processing questions
- Dispute-management failures
- Incorrect platform behavior
- Account configuration
Contact the issuing bank
A cardholder contacts the bank when formally disputing an unauthorized or unresolved charge. Once that occurs, the dispute moves through the issuing bank, card network, Finix, and merchant response process.
Do not send the buyer to Finix merely because the Finix name appeared during checkout. Finix may have processed the payment without being the seller.
Finix pricing needs product-specific verification
Finix publishes different pricing structures for direct merchants and payment platforms.
Its current US direct-merchant page lists pricing starting at $250 monthly. The same page directs larger merchants and businesses with different processing needs to contact the sales team for account-specific terms.
For platforms, marketplaces, and payment facilitators, Finix currently lists merchant-management charges that include:
- $0.25 per merchant payout
- $5 one-time merchant-onboarding fee
- $2.50 per active merchant each month
- $5 per year for 1099-K issuance
Finix also publishes comparison content mentioning subscriptions starting at $99 per month, while the dedicated direct-merchant pricing page displays a $250 starting amount. This difference means the exact product, eligibility, and commercial offer must be verified before publishing a cost estimate.
Use the dedicated pricing page and written quote. Skip blended figures taken from unrelated Finix products.
Common Finix mistakes
A buyer tries to log in for a refund
Refund requests begin with the merchant, not the business dashboard.
A merchant calls a refund a chargeback
A refund is merchant-initiated. A chargeback begins through the cardholder’s issuing bank.
A team responds after the dispute deadline
Finix expects merchants to act within the deadline displayed for the case. Review active disputes before routine reporting.
A user resets a password during an MFA issue
Administrators can reset a team member’s MFA under Company > Team > Members.
A business assumes every refund erases the original transaction
Finix keeps the original payment and refund as related money-movement records.
Frequently asked questions
Is Finix a bank?
No. It is a payment technology provider.
Can a customer log in to request a refund?
Usually not. Contact the merchant.
Can Finix issue a partial refund?
Yes. Finix documents both full and partial refunds through the Dashboard, API, or a supported terminal.
Is a refund the same as a chargeback?
No. A merchant issues a refund; a cardholder starts a chargeback through the issuing bank.
How long can a Finix dispute take?
Finix says the full process commonly takes two to three months and can rarely extend to six months.
Why was money removed from a merchant settlement?
When a dispute is created, Finix says the disputed funds are debited from the merchant through a settlement. Refunds and other adjustments can also affect settlement totals.
Can an administrator reset Finix MFA?
Yes. Administrators and User Management Admins can reset MFA for individual team members through the Team Members page.
Who decides whether a merchant wins a dispute?
The issuing bank reviews the evidence and decides the outcome under the applicable card-network process.