Finix Payments
Finix is a full-stack payments technology provider that lets businesses, software platforms, and marketplaces accept and send payments online and in person. Its REST API (version 2022-02-01) covers the full payments lifecycle — Identities, Merchants, Payment Instruments, Authorizations, Transfers, Settlements, Disputes, Verifications, Fee/Payout Profiles, Devices/terminals, and Webhooks — enabling card, ACH, EFT, digital-wallet, and Buy-Now-Pay-Later acceptance, seller onboarding/underwriting, split transfers, payouts, and payment facilitation (PayFac-as-a-service). Finix is a Level 1 PCI DSS certified platform with browser (finix.js) and mobile tokenization SDKs, hosted checkout pages, and payment links. Authentication is HTTP Basic Auth with environment-scoped API keys; the API uses cursor pagination, idempotency_id request-level idempotency, HAL responses, and dated versioning via the Finix-Version header.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Finix Payments the way a machine reads it — 28 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Finix Payments scores 60.9/100 (strong), with a separate agent-readiness read of 87/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Finix Payments
Each block below is one kind of artifact we hold for Finix Payments. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Finix Payments Authorizations API
{'$ref': 'api-descriptions/tags/authorizations.md'}
Finix Payments Balance Transfers API
{'$ref': 'api-descriptions/tags/balance-transfers.md'}
Finix Payments Compliance Forms API
{'$ref': 'api-descriptions/tags/compliance-forms.md'}
Finix Payments Devices API
{'$ref': 'api-descriptions/tags/devices.md'}
Finix Payments Disputes API
{'$ref': 'api-descriptions/tags/disputes.md'}
Finix Payments Fee Profiles API
{'$ref': 'api-descriptions/tags/fee-profiles.md'}
Finix Payments Files API
{'$ref': 'api-descriptions/tags/files.md'}
Finix Payments Identities API
{'$ref': 'api-descriptions/tags/identities.md'}
Finix Payments Instrument Updates API
{'$ref': 'api-descriptions/tags/instrument-updates.md'}
Finix Payments Merchant Profiles API
{'$ref': 'api-descriptions/tags/merchant-profiles.md'}
Finix Payments Merchants API
{'$ref': 'api-descriptions/tags/merchants.md'}
Finix Payments Onboarding Forms API
{'$ref': 'api-descriptions/tags/onboarding-forms.md'}
Finix Payments Payment Instruments API
{'$ref': 'api-descriptions/tags/payment-instruments.md'}
Finix Payments Payout Profiles API
{'$ref': 'api-descriptions/tags/payout-profiles.md'}
Finix Payments Settlements API
{'$ref': 'api-descriptions/tags/settlements.md'}
Finix Payments Split Transfers API
{'$ref': 'api-descriptions/tags/split-transfers.md'}
Finix Payments Transfers API
{'$ref': 'api-descriptions/tags/transfers.md'}
Finix Payments Verifications API
{'$ref': 'api-descriptions/tags/verifications.md'}
Finix Payments Webhooks API
{'$ref': 'api-descriptions/tags/webhooks.md'}
Scroll within the panel for all 19 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOFinix — Accept a card payment (auth + capture)
Create a buyer Identity, tokenize a card, authorize, then capture into a Transfer.
ARAZZOFinix — Onboard a seller/merchant
Create a seller Identity, provision a Merchant, and run verification/underwriting.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
finix-payments-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Finix Payments Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Finix Payments Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Finix Payments — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/finix-payments · machine-readable index on apis.io