By Marcus Reed, payment operations analyst with 7 years of merchant-support experience
Last reviewed: July 30, 2026
Finix is a business payment processor and infrastructure platform used to accept payments, manage transactions, onboard merchants, and distribute funds. Current customers access their account through the Finix Dashboard, while businesses evaluating the service can create a separate sandbox for testing.
This article is independently published and is not affiliated with Finix Payments, Inc. Account activation, live processing, pricing, and access changes should be confirmed through Finix’s own website, documentation, or assigned representative.
What Finix does
Finix combines payment processing with operational tools for direct merchants, software companies, marketplaces, and payment facilitators. Businesses can manage payment activity through application programming interfaces, a web dashboard, or lower-code products such as payment links and a virtual terminal.
That description covers several different use cases.
A retailer might use Finix to process its own online and in-store sales. A software company might embed payment acceptance into its product so its customers can charge buyers. Another company may use Finix primarily to send payouts to recipients through bank or card rails.
These are not identical account arrangements. They can have different onboarding requirements, enabled products, pricing, permissions, and reporting structures.
Finix is not a consumer bank account or peer-to-peer wallet. A customer who sees “Finix” on a payment-related record may have paid a business that uses Finix behind the scenes rather than having a direct Finix account.
Finding the correct Finix login
The safest route to the dashboard is the Log In link shown on the Finix website or at the top of its documentation. Finix currently links that control to its payment dashboard and displays Create Sandbox separately for businesses beginning a test integration.
Do this first: open the Finix website yourself and select Log In. Skip search advertisements or unofficial pages that merely include the company name.
An invited user should normally sign in under the organization that added them. A business evaluating Finix may instead need the sandbox-registration flow. Creating a sandbox does not automatically indicate that the business has live payment-processing access.
The distinction is easy to miss.
Finix maintains separate sandbox and live environments. The sandbox is designed for development and testing; the live environment handles actual payment activity. Each environment also has its own API credentials.
Dashboard login and API access are different
A dashboard user signs in to operate an account through the web interface. A developer authenticates API calls using credentials generated for the relevant environment.
Those credentials are not interchangeable.
Finix’s API documentation says requests use HTTP Basic Authentication. It also confirms that sandbox and live accounts are separate and do not share API credentials. Sending the right request to the wrong environment can therefore fail even when the credential pair itself was entered correctly.
The API reference identifies several useful status codes:
| Code | Meaning in Finix documentation |
|---|---|
| 400 | The request could not be parsed |
| 401 | The request could not be authenticated |
| 403 | The credentials lack permission |
| 404 | The requested resource was not found |
A 401 should lead you to check authentication and environment selection. A 403 points more directly toward access rights. Replacing credentials immediately is not always the right move.
For browser access, ignore API troubleshooting entirely unless you are working on an integration. Start with the dashboard invitation, user status, and multi-factor authentication.
Why Finix may request an authentication code
Finix supports multi-factor authentication through SMS or a mobile authenticator. Its documentation specifically mentions options such as Google Authenticator and Okta, along with other compatible providers.
When MFA has been enabled, Finix asks for the additional code during dashboard login. Company administrators and User Management Admins can also enforce MFA for team members listed in the company’s Team area.
This creates several recognizable access problems:
- The user changed phones and no longer has the configured authenticator.
- The company now enforces MFA, but the user has not completed setup.
- The user expects an SMS while the account is configured for an authenticator.
- A former or inactive team membership is being used.
- The user is opening a sandbox account when the intended work is in live.
For a team member who has lost the second authentication method, Finix documents an administrator reset path under Company > Team > Members. The administrator selects the relevant member and uses Reset Multi-Factor Authentication.
Ask the account administrator to check this before creating a second profile. Duplicate profiles can make permissions and organization selection harder to untangle.
What appears inside the Finix platform
Finix describes its product as an end-to-end payment platform that covers acceptance, settlement, reporting, merchant onboarding, risk processes, and payouts. The exact dashboard experience is customized according to the business type and enabled services.
One user may primarily review online payments. Another may work with merchant applications, disputes, settlement records, payment devices, or payout activity.
Finix also publishes several lower-code and no-code products:
- Payment Links
- Virtual Terminal
- Invoices
- Subscriptions
- Checkout tools
- Merchant onboarding forms
The documentation lists these as separate product areas rather than treating the dashboard as one universal screen for every account.
That matters when a menu item is missing. The feature may not be enabled for the organization, or the current user may not have the required role.
Do not assume a hidden feature is a system outage.
Finix for direct merchants versus platforms
Finix publishes different product and pricing paths for businesses processing their own sales and businesses processing for other merchants.
A direct merchant accepts payment for its own goods or services. A software platform or marketplace may onboard sellers and place payment functions inside its own product. Finix also has a dedicated payout offering for companies that primarily need to send funds to bank accounts or cards.
Before contacting sales, answer one operational question: Who is actually selling to the end customer?
If it is your company, review the direct-merchant path first. If independent sellers use your software and receive the proceeds, the platform or marketplace path is more relevant. If you are distributing funds rather than collecting customer payments, examine payouts.
This classification affects far more than marketing language. It can influence onboarding responsibilities, transaction structure, reporting, settlement, compliance workflows, and contract pricing.
Current Finix direct-merchant pricing
For US direct merchants, Finix currently publishes a standard processing subscription starting at $250 per month. The pricing page lists card-present processing at $0.08 and card-not-present processing at $0.15, with interchange and network fees passed through at zero Finix markup under that standard table. American Express processing is listed at 0.30% per transaction.
The same page currently shows:
- Subscription billing: 0.4%
- ACH validation: $0.55
- ACH returns: $5 each
- ACH instant payout: 1.5%
- Card and ACH disputes: $30
- Plaid integration: $3
For same-day ACH entries, the published standard rate is 1%, with a $1 minimum and $10 maximum. Businesses processing more than $1 million annually are directed toward custom pricing. Finix also says the subscription tier is determined by transaction volume and may rise after specified volume thresholds are exceeded.
Rates vary by product, geography, volume, and contract. The direct-merchant schedule should not be applied automatically to a marketplace or payout program.
Finix payout pricing is separate
Finix maintains another pricing page for payouts. It currently lists a monthly recurring charge starting at $250, a $0.25 card payout-processing fee, a $0.25 next-day ACH-processing fee, and a $0.75 same-day ACH-processing fee. Third-party charges are described as pass-through costs.
This is a useful distinction because “accepting a payment” and “sending a payout” are separate operations.
A merchant receiving card payments should not estimate costs from the payout table. Likewise, a company distributing earnings to workers, sellers, or other recipients should not rely only on the direct-merchant card rates.
Compare the correct product page first, then review the written offer.
Is Finix suitable for a small business?
Possibly, but the published subscription model deserves close attention.
Finix includes tools that can reduce development work, including payment links, a virtual terminal, hosted checkout options, and dashboard reporting. Its direct-merchant pricing may appeal more to businesses whose processing volume justifies a monthly subscription and interchange-based pricing.
A very small or occasional seller should calculate total monthly cost rather than comparing only the per-transaction amount. A higher-volume merchant may reach a different conclusion.
Use estimated monthly volume, average transaction size, card-present versus online mix, American Express share, ACH use, disputes, and any required add-ons. Skip comparisons based on one headline rate.
Where to get Finix help
Finix’s site provides separate routes for dashboard login, documentation, API status, sales contact, complaints, and its Trust Center. The pricing pages currently publish a sales number of 866-554-0994 for pricing discussions.
Use the channel that matches the problem:
- Ask your organization’s administrator about invitations, roles, and MFA resets.
- Use Finix documentation for product behavior and API errors.
- Check Finix API Status when an integration appears broadly unavailable.
- Contact the assigned Finix representative for live-environment access or contract matters.
- Use Finix’s published sales route for pricing and account evaluation.
A support request should describe the environment, approximate incident time, affected function, and visible error wording. Never include authentication credentials, payment-security codes, or confidential customer records.
Frequently asked questions
Is Finix a payment gateway?
Finix offers gateway functions, but describes itself more broadly as an end-to-end payment processor and platform covering payments, operations, merchant onboarding, reporting, settlement, and payouts.
Can I log in as a customer who paid a Finix merchant?
Usually not.
The dashboard is intended for businesses and authorized team members using Finix products. A buyer with a question about a purchase should normally contact the merchant shown on the receipt or statement.
Can I test Finix without processing real payments?
Yes. Finix provides a sandbox environment for development and testing. Sandbox and live activity remain separate.
Why does my Finix API return 403?
Finix defines 403 Forbidden as a request made with credentials that do not have the correct permissions. Check the credential’s environment and assigned access before changing the request body.
Does Finix support in-person payments?
Yes. Finix says online and in-person activity can be managed through the same broader platform, with supported devices and products depending on the business configuration.
Does Finix have payment links?
Yes. Finix lists no-code payment links as a platform feature.
Can an administrator reset a user’s MFA?
Yes. Finix documents an MFA reset action for Administrators and User Management Admins through the Team Members area.
Is Finix pricing the same for every company?
No. Finix separates direct-merchant, platform, marketplace, and payout pricing, with custom terms available for some processing profiles.