Platform — Developer access
Build onPixely
Developer-first APIs and SDKs for payments, wallets, identity, intelligence and compliance, on one platform. They are being built now; the sandbox and the reference open by request.
01 — What you will get
Everything the platform does, by call.
The same platform the services run on, exposed to your own code — so what you build inherits the identity, the ledger and the controls underneath.
A REST API
Payments, wallets, identity, decisioning and reporting behind one consistent API — one shape of request and one shape of error across every service.
SDKs and capture kits
Client libraries for the server, and drop-in kits for web and mobile that handle document and face capture on the device.
A sandbox
A full copy of the platform with test data and no real money, to build and break against before anything goes near the rails.
Events and webhooks
Every posting, approval and settlement as an event, delivered to your endpoint — so your systems hear what happened rather than polling for it.
Scoped keys
Keys scoped to what they are for, mutual TLS and replay windows: the application layer of the platform's security, in your hands.
The reference
Documentation for every endpoint, event and error, written alongside the platform and shared with developers as access opens.
The platform is being built. The sandbox, the API reference and the SDKs are shared by request, not publicly available yet.
02 — The shape of a call
Say what should happen.
A request names the outcome; the platform is designed to handle the rest — the rail, the approvals, the record — and to tell you about each step as an event.
Request
Illustrative
POST /v1/paymentsIdempotency-Key: run-2026-08-payroll{ "from": "acct_dzd_payroll", "rail": "auto", "reference": "RUN-2026-08", "approvals": "policy"}Events, in order
evt payment.initiated atcievt policy.approval.required payrollevt policy.approval.granted payrollevt ledger.debit.posted dzd_payrollevt payment.settled atciIdempotent
Every write carries a key, so a retried request is recognised rather than repeated. A payment is sent once.
Rail-agnostic
Name the rail or leave it to the platform. The request is the same shape either way.
Policy-aware
Approvals are part of the call's life. A request above your threshold waits, and says so.
Evented
Each step is announced as it happens, in the order it happened.
03 — How to get access
Ask, and we will open it.
Access is by request while the platform is being built, and every request is read by the team building it.
- 01
Ask
Tell us what you are building through the developer access form — the product, the services it needs and the timeline.
- 02
Talk
An engineer follows up to understand your use case and what you need from the platform first.
- 03
Sandbox
As access opens, you get the sandbox, the reference and the keys to build against it.
- 04
Build
Integrate against test data, with the people building the platform a message away.
04 — Developer access
Requestaccess
Tell us what you are building, and we will be in touch about the sandbox, the reference and the SDKs.