We got tired of payments being a project.
Fluxpay is what happens when the people who lost whole quarters to underwriting forms and reconciliation files decide to build the payments API they always wanted. One honest endpoint, your brand on the statement, live in minutes.
Why we exist
We were engineers before we were a payments company. We'd shipped the products around the charge — the cart, the dashboard, the payout email — and every single time the payment itself was the part that turned a two-week build into a two-quarter saga.
Underwriting that needed a PDF and a phone call. A PCI audit that ate a sprint. Reconciliation that lived in a fragile spreadsheet nobody wanted to own. The money moved, eventually, but reading where it went felt like archaeology. We kept thinking the same thing on every project.
Payments should be one honest API — not a department, not a deadline, not a leap of faith.
So we built it. Cards tokenized in the browser so card data never touches your servers. A real-time ledger you can query instead of a nightly file you have to trust. Webhooks that are signed, ordered and replayable. SDKs generated from one spec and hand-tuned until they felt good to hold. Fluxpay is the payment facilitator we wished existed — so we stopped waiting and wrote it.
The opinions baked into the API
Four convictions that decide what we build and, just as often, what we refuse to ship.
APIs over forms
If a thing can be done in code, it should be. No PDFs to fax, no portals to click through — every capability is one typed, versioned endpoint.
Money you can read
A real-time, queryable ledger behind every charge, transfer and payout. You should never have to guess where a cent went or wait for a nightly file.
Boring reliability
99.99% rolling uptime, signed and ordered webhooks, idempotent writes. Payments should be the least exciting part of your week.
Builders first
Docs written by people who shipped the SDK, a cURL on every log line, and a sandbox you can break freely. DX is the product, not a footnote.
From a tired team to 135+ currencies
A short history, told in the things that actually mattered.
- Day zero
Founded by tired engineers
Three of us had just lost a quarter to underwriting, a PCI audit and a reconciliation spreadsheet. We started writing the payments API we wished we'd had.
- First quarter
First live charge
Eleven lines of code, a tokenized card, and a real settlement. The drop-in tokenizes client-side, so SAQ-A scope came for free.
- Year one
SDKs in six languages
Node, Python, Go, Ruby, PHP and Rust — generated from one spec, hand-tuned for ergonomics, with a cURL on every log line.
- GA
Programmable money flows
Split a single charge across any number of accounts, define fees and holds in code, and settle automatically against a real-time ledger.
- Today
135+ currencies, one integration
Cards, wallets, ACH and SEPA behind a single API, with 99.99% rolling uptime and signed, replayable webhooks across every region.
Who we are
We're a small, remote, builder-led team spread across time zones, united by a low tolerance for ceremony and a high one for edge cases. No sales-driven roadmap, no headshots to memorize — just people who read the logs. Fluxpay is a working name; the standards behind it aren't placeholders.
Build the payments you wished you'd had
Spin up a sandbox, copy a test key and POST your first charge in eleven lines. No sales call, no waiting on underwriting to start building.