Home / Developers
◆ Developers · API v1
Money movement,
one request away.
A predictable REST API for payments, routing, payouts and ledgers. Sandbox in minutes, production when you're ready.
Base URL
api.paxora.example/v1
Format
REST · JSON · HTTPS
Sandbox
Free, no real money
— 01 / Overview
An API that behaves
the way you expect.
Resource-oriented URLs, JSON in and out, standard HTTP codes. Every object carries an ID you can trace from request to settlement.
P.01
Predictable
Nouns for resources, verbs for actions. /v1/payments works the way /v1/payouts does.
P.02
Versioned
Pin a version per key. Breaking changes ship under a new version — never silently.
P.03
Safe to retry
Send an Idempotency-Key and a retried request can never charge twice.
P.04
Event-driven
Signed webhooks tell you when money moves, so you never poll for status.
Response codesFictional example API
decline_code— 02 / API
Four layers.
One reference.
Endpoints are grouped by the clearing layer they act on. Choose a layer to filter the reference.
Showing all 16 endpoints
/v1/paymentsCreate a payment01 API/v1/payments/{id}Retrieve a payment and its full timeline01 API/v1/refundsRefund all or part of a payment01 API/v1/customersStore a customer and their payment methods01 API/v1/routing/rulesCreate a routing rule by card, country or amount02 Routing/v1/routing/decisions/{id}Explain why a payment took its route02 Routing/v1/processorsConnect an additional processor02 Routing/v1/payments/{id}/captureCapture an authorised payment03 Processing/v1/risk/assessmentsScore a payment before you submit it03 Processing/v1/disputesList open disputes and deadlines03 Processing/v1/disputes/{id}/evidenceSubmit evidence for a dispute03 Processing/v1/balancesLive balances per currency and account04 Settlement/v1/payoutsSend funds to a bank account04 Settlement/v1/virtual_accountsOpen a virtual account for a customer or entity04 Settlement/v1/ledger/entriesRead double-entry ledger lines04 Settlement/v1/reconciliation/reportsDaily reconciliation, matched to the cent04 Settlement— 03 / Quickstart
From zero to first payment
in four steps.
Everything below runs in the sandbox. No real money moves until you switch to live keys.
01
Step 01 · ~2 min
Get sandbox keys
Request a sandbox. Test keys appear in your dashboard — publishable for the browser, secret for your server.
02
Step 02 · ~1 min
Install an SDK
Official libraries wrap authentication, retries and idempotency for you. Prefer raw HTTP? cURL works too.
03
Step 03 · ~5 min
Create a payment
One call. PAXORA routes it, authorises it and schedules settlement — the response tells you exactly what happened.
04
Step 04 · ~5 min
Listen for webhooks
Forward sandbox events to your machine, verify the signature, and update your order when payment.succeeded arrives.
● Go live · swap sk_test_ for sk_live_ once your account is reviewed
— 04 / Examples
Same payment.
Your language.
Create a €1,240.00 payment with smart routing and a settlement account. Copy any tab — the response is identical.
route.reasonWhy the routing layer chose this processor — no black box.settlement.expectedWhen the funds land in the settlement account.— 05 / Auth
Every request proves
who sent it.
Keys identify you, scopes limit what they can do, signatures prove our webhooks are ours, and idempotency keys make retries safe.
A.01
API keys
Authenticate with HTTP Basic auth: your secret key is the username, the password is empty. Keys are prefixed by type and mode, so a test key can never touch live money.
pk_
publishable — safe in the browser
sk_
secret — server only, never in client code
rk_
restricted — limited to the scopes you choose
A.02
Scopes
Give every service the smallest key it needs. A checkout service can create payments without ever being able to send a payout.
Restricted key ·checkout-service
A.03
Signed webhooks
Every event carries a Paxora-Signature header: a timestamp and an HMAC-SHA256 of the raw body, signed with your endpoint secret. Verify it before you trust the payload, and reject anything older than five minutes.
A.04
Idempotency keys
Networks fail. Send a unique Idempotency-Key with every POST and we store the first result for 24 hours — a retry returns that same result instead of creating a second payment.
— 06 / SDKs
Libraries for
the stack you run.
Typed clients with retries, pagination and idempotency built in.
JS
Node.js
v4.2.0 · TypeScript types
PY
Python
v3.8.1 · async + sync
GO
Go
v2.5.0 · context-aware
RB
Ruby
v3.1.4 · Rails-friendly
JV
Java
v5.0.2 · JDK 17+
PHP
PHP
v2.9.0 · PSR-18 client
Integrations & tooling
Webhook CLI
Forward sandbox events to localhost and replay any of them.
● Available
API collection
Every endpoint, pre-authenticated, for your API client of choice.
● Available
Accounting export
Daily journal files mapped to your chart of accounts.
● Beta
Data warehouse sync
Ledger and payment tables, refreshed hourly.
● Beta
— 07 / Docs
Documentation index.
Jump to any part of this page, or ask an engineer directly.
D.01
Quickstart
First payment in four steps
→
D.02
API reference
Endpoints by clearing layer
→
D.03
Code examples
cURL, Node.js, Python, Go
→
D.04
API keys
Types, modes and rotation
→
D.05
Scopes
Least-privilege restricted keys
→
D.06
Webhooks
Events and signature checks
→
D.07
Idempotency
Retry without double charges
→
D.08
SDKs & tooling
Six languages, CLI, exports
→
D.09
Changelog
What shipped this month
→
◆ $ paxora init
Start building in the sandbox.
Test keys today. A solutions engineer when you're ready for production.