Login
Integrations

Connect what
you run

Your bank, books and store kept in agreement — by agents, with your team signing off.

See the WooCommerce plugin
100+ integrations · one plugin to install · one API to build on
Pick your platform

Select what you run to see how it connects

100+ integrations. The ones with a page of their own come first.

WooCommerce
WooCommerceOrders paid on a hosted checkout, confirmed by signed webhooks, refunded from the order screen.
QuickBooks
QuickBooks OnlineInvoices, payments and bills read as they change; job references and reminders written back.
Plaid
Plaid
PlaidBank accounts, balances and transactions, read through Plaid and matched to what you're owed.
monday.com
monday.comJobs read from your boards; status, group and new items written back when the money moves.
Notion
Notion
NotionJobs and clients read from a Notion database, matched to invoices, payments and payouts.
Asana
Asana
AsanaTasks read from an Asana project as jobs, matched to invoices, payments and payouts.
Google Sheets
Google Sheets
Google SheetsA sheet read as your job or payee list, kept in step as the rows change.
Xero
XeroAccounting stack
FreshBooks
FreshBooksAccounting stack
Sage
Sage
SageAccounting stack
NetSuite
NetSuite
NetSuiteAccounting stack
Wave
Wave
WaveAccounting stack

Didn't find your platform? Anything with an export or an API can be connected.

Your customers pay however they already pay — Visa, Mastercard, American Express, Apple Pay, Google Pay, Faster Payments, bank transfer and open banking — through the provider you run today or through us.

Three ways in

Install it, connect it, or build on it

Pick the one that matches how technical your team is. Most businesses use two.

Install a plugin

For stores. Upload the Fynex plugin, paste one token, and orders are paid, confirmed and refunded without touching your checkout code. WooCommerce today.

Connect from the dashboard

For everyone. Link your bank, your accounting system and the tools the work runs in. Fynex reads them and writes back — no code, no export files.

Build on the API

For product teams. Checkout, splits, payouts, wallets and webhooks as one REST and GraphQL surface, with an OpenAPI spec your agent can read.

POST /payments-api/v1/checkout
What a connection gives you

What happens once your tools are connected

Connecting a tool is not the value. What runs on top of the connection is.

  1. 1

    Reads what's already there

    Orders, invoices, contracts, bank balances and payouts, pulled from the systems you connected — nothing retyped, nothing exported.

  2. 2

    Decides how the money should move

    Who is owed what, on which terms, and through which rail it lands cheapest — your rules, applied to every transaction, not a spreadsheet's guess.

  3. 3

    Moves it and writes the record back

    Pays out over the rail you keep or over Fynex's own — settled through Banking Circle — then posts the result to your books, so the bank, the invoice and the ledger agree.

Build on it

Drive Fynex from your own system

Four requests from the published Payments API. Each one is documented, versioned and runnable against a demo token.

Hosted checkout

Take a payment without building a checkout

Create a hosted checkout for an amount and a currency; send the customer to the URL you get back.

POST /payments-api/v1/checkout
{ "amount": 129.00,
  "currencyCode": "GBP",
  "autoSettlement": true }
Hosted checkout reference →
Splits

Divide a payment before it lands

Each party's share is a line in a versioned rule — the seller, your fee, a partner cut — resolved at settlement.

GET /payments-api/v1/payments
  /ORDER-100106/split-decisions
→ { "decisions": [{ "id": "decision-1", "paymentId": "ORDER-100106", "ruleId": 7, "ruleVersion": 3, "inputs": { "ruleId": 7, "ruleVersion": 3, "allocationMode": "absolute", "amountBase": "net_settled", "grossAmountMinor": 10000, "lines": [{ "payeeId": 101, "priority": 1, "isEnabled": true }] }, "rulesApplied": [], "rulesSkipped": [], "outcome": { "shares": [{ "payeeId": 101, "rawShareMinor": 8000, "shareAmountMinor": 8000, "feeAmountMinor": 0, "netAmountMinor": 8000 }], "totalFeeMinor": 0, "grossAmountMinor": 10000, "remainderMinor": 2000, "overAllocated": false }, "evaluatedAt": "2026-09-02T12:34:56Z" }] }
Splits reference →
Payouts

Pay every party on the right rail

SEPA, Faster Payments or cross-border, chosen from the payout currency and the account the payee registered.

POST /payments-api/v1/payouts
{ "walletId": 15,
  "payoutMethodId": 501,
  "currencyCode": "GBP",
  "amount": "420.00" }
Payouts reference →
Webhooks

Hear about every event, signed

Register an endpoint once; every payment, refund and payout event arrives signed with a secret only you hold.

POST /payments-api/v1/webhooks
{ "webhookUrl":
  "https://you.example/fynex" }
→ { "secretKey": "whsec_…" }
Webhooks reference →
FAQ

Questions, answered

No. The WooCommerce plugin installs from a zip and connects with one token. Bank, accounting and the tools you run the work in are connected from the Fynex dashboard, and the finance work between them runs on its own. The API is there when your team wants to drive Fynex from your own product.
No. Fynex sits on top of them. It reads what your bank, your books and your store already hold, does the calculations between them — who is owed what, on which terms, through which rail — and writes the result back to the system you already trust.
The next action, not another dashboard. Once a tool is connected, Fynex uses its data to decide who to pay, how much, through what, and when — then executes it and posts the record back, so your bank, your invoices and your accounting agree without anyone reconciling them.
Tell us which one. The catalogue is 200 tools and growing, and the API and webhooks cover anything with an export. Send the name through the form on this page and we will say what connecting it looks like for your setup.
Both. Fynex accepts payments, pays out to suppliers, contractors and sellers, and holds balances per party — and where you already have a rail that works, it routes over that one instead of replacing it.
We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.

Keep your stack. Let Fynex run the money between it

Get in touch
Spreadsheets, retired with honours.Month-end close, minus the month-end.FX fees, caught red-handed.Fewer tools. Fewer tabs. Fewer tears.Your CFO's favourite coworker never takes lunch.Spreadsheets, retired with honours.Month-end close, minus the month-end.FX fees, caught red-handed.Fewer tools. Fewer tabs. Fewer tears.Your CFO's favourite coworker never takes lunch.Spreadsheets, retired with honours.Month-end close, minus the month-end.FX fees, caught red-handed.Fewer tools. Fewer tabs. Fewer tears.Your CFO's favourite coworker never takes lunch.
Book a demo