Build with Fluxpay
One typed, versioned API to charge cards, split funds, run payouts and listen to events. Idempotent by default, six official SDKs, and a sandbox you can hit in the next eleven lines of code.
From signup to live charge in three steps
No sales call, no underwriting queue. Copy a test key and start hitting the API immediately.
Grab your keys
Sign up and copy a test secret key from the dashboard. No sales call, no waiting on underwriting to start building.
export FLUXPAY_KEY=sk_test_51H…Create a charge
Install an SDK and POST to /v1/charges. Tokenize the card in the browser, confirm 3-D Secure, done.
flux.charges.create({ amount: 1900, currency: "usd" })Go live
Complete KYB, flip to live keys and point a webhook at your app. Your name lands on the customer's statement.
flux.webhooks.verify(req.headers, body, secret)Install once, ship in your language
Hand-written, fully typed clients for six runtimes — all tracking the same versioned API.
npm i @fluxpay/node
pip install fluxpay
go get flux.dev/fluxpay-go
gem install fluxpay
composer require fluxpay/fluxpay-php
cargo add fluxpayA small, predictable REST surface
Resource-oriented endpoints, idempotency keys on every write, and cursor pagination throughout.
- POSTCreate a charge
/v1/charges - POSTPay out to an account
/v1/payouts - POSTOnboard a sub-merchant
/v1/accounts - GETRead available balance
/v1/balance - POSTMove funds between accounts
/v1/transfers - GETList & replay webhook events
/v1/events
Signed, ordered, replayable events
Every state change is delivered as a signed webhook with automatic retries for 72 hours and a local tunnel for testing. Replay any event from the dashboard or the /v1/events API.
Infrastructure you can watch in real time
Uptime and latency for every component, published openly. Subscribe for incident updates the moment they happen.
- Payments APIOperational
- DashboardOperational
- WebhooksOperational
- PayoutsOperational
Your first live charge is eleven lines away
Spin up a sandbox in seconds. Bring it to production whenever you’re ready — same API, same SDKs, your brand on the statement.