Platform — APIs and SDKs
Build onPixely
Developer-first APIs and SDKs for straightforward integration: accounts, payments, identity checks and fraud screening behind one platform, so a team builds its product rather than a stack of providers.
01 — One integration
The whole platform, one API.
Every service on Pixely is reachable the same way: a resource, a request and an answer, with an event when anything changes. Four of them, sketched.
AccountsIllustrative
POST /accounts{ "holder": "hld_…", "currency": "DZD", "purpose": "operating"}201 Created{ "id": "acc_…", "currency": "DZD", "status": "open"}The shape of the thing, not its reference. Paths and fields are sketched to show what each resource does; the API reference comes with sandbox access.
02 — Built for builders
The details that save a quarter.
An API is judged in the week after the first call. These are the parts the platform is designed around, so that week is short.
Predictable by design
Resources named for what they are, JSON in and out, and errors that say what went wrong and what to do about it.
Safe to retry
Idempotency keys on every call that moves money, so a dropped connection never becomes a payment made twice.
Signed events
Webhooks for every state change, each one signed and replay-protected, so your system can trust what it hears.
Scoped keys
Keys that can do only what they were issued for, mutual TLS for the calls that matter, and every request signed.
SDKs and capture kits
Client libraries for the server, and drop-in kits for web and mobile that handle the camera, the chip and the card.
A sandbox with rails
Simulated ARTS, ATCI and SWIFT to build against, with test identities and failures you can trigger on purpose.
03 — How it runs
From a key to launch.
Four movements, and the third one is ours as much as yours: nothing goes live on the platform without a review.
- 01
Sandbox
Ask for access and get keys to an environment with simulated rails, test identities and the full set of resources.
- 02
Build
Open accounts, move money and prove people against the sandbox, with webhooks arriving exactly as they will in production.
- 03
Review
Before go-live, your integration, your flows and your policies are reviewed with an engineer.
- 04
Launch
The same calls, pointed at production. Nothing in your code changes but the key.
04 — Get started
Ask for thesandbox
Tell us what you are building, and ask for sandbox access and the API reference.