Developers

Build on a clean, predictable API.

REST endpoints, typed SDKs, idempotency, and signed webhooks. Integrate acceptance, orchestration and settlement in days — with a sandbox that mirrors production.

Quickstart

One call, any rail

Create a payment and let the platform screen, route and settle it. Everything is idempotent and observable end to end.

// Node — install @flowapay/node
import Flowa from "@flowapay/node";
const flowa = new Flowa(process.env.FLOWA_KEY);

const payment = await flowa.payments.create({
  amount: "1200.00", currency: "EUR",
  method: "auto", settlement: "instant"
}, { idempotencyKey: "ord_1837" });

payment.status; // "settled"

Reference

Core endpoints

POST/v1/paymentsCreate and route a payment across any rail

GET/v1/payments/:idRetrieve a payment and its status timeline

POST/v1/refundsIssue a full or partial refund

POST/v1/payoutsSend a payout over real-time rails

POST/v1/customersCreate a customer and store verification

GET/v1/balancesRead settled and available balances

Architecture

One API over every capability

A single gateway fronts acceptance, orchestration and settlement, with risk controls in-line and a ledger underneath. Webhooks and SDKs keep your systems in sync.

Idempotent, versioned REST API
Signed webhooks with retries
SDKs for Node, Python, PHP, Go & more
Sandbox parity with production

FAQ

Developer FAQ

Yes — a sandbox that mirrors production behaviour, with test keys and simulated provider responses.

Every webhook is signed; verify the signature with your endpoint secret. Deliveries are retried with backoff.

Yes. Breaking changes ship under a new version; existing versions remain supported with advance notice.

Start building today

Create sandbox keys and integrate the core API in days, not quarters.

Speak to an expert →Read the docs